User equipment, base stations and signaling for multiple active configured grants

ABSTRACT

A user equipment (UE) is described. The UE includes receiving circuitry configured to receive a common configuration comprising parameters shared by multiple configured grants. The UE also includes transmitting circuitry configured to perform, based on the parameters shared by the multiple configured grants of the common configuration, transmissions on a physical uplink shared channel (PUSCH).

CROSS REFERENCE

This Nonprovisional application claims priority under 35 U.S.C. § 119 onprovisional Application No. 62/842,129 on May 2, 2019, the entirecontents of which are hereby incorporated by reference.

TECHNICAL FIELD

The present disclosure relates generally to communication systems. Morespecifically, the present disclosure relates to user equipment (UE) andbase stations and signaling for multiple active configured grants.

BACKGROUND ART

Wireless communication devices have become smaller and more powerful inorder to meet consumer needs and to improve portability and convenience.Consumers have become dependent upon wireless communication devices andhave come to expect reliable service, expanded areas of coverage andincreased functionality. A wireless communication system may providecommunication for a number of wireless communication devices, each ofwhich may be serviced by a base station. A base station may be a devicethat communicates with wireless communication devices.

As wireless communication devices have advanced, improvements incommunication capacity, speed, flexibility and/or efficiency have beensought. However, improving communication capacity, speed, flexibilityand/or efficiency may present certain problems.

For example, wireless communication devices may communicate with one ormore devices using a communication structure. However, the communicationstructure used may only offer limited flexibility and/or efficiency. Asillustrated by this discussion, systems and methods that improvecommunication flexibility and/or efficiency may be beneficial.

SUMMARY OF INVENTION

In one example, a user equipment (UE) that communicates with a basestation comprising: receiving circuitry configured to: receive a RadioResource Control (RRC) message including first information indicating arepetition type for a first configured grant (CG) Physical Uplink SharedChannel (PUSCH) transmission, receive a RRC message including secondinformation indicating a repetition type for a second CG PUSCHtransmission, receive a RRC message including third informationindicating whether codebook based transmission or non-codebook basedtransmission is used for the first CG PUSCH transmission and the secondCG PUSCH transmission, transmitting circuitry configured to: perform thefirst CG PUSCH transmission based on the first information and the thirdinformation, perform the second CG PUSCH transmission based on thesecond information and the third information.

In one example, a base station apparatus that communicates with a userequipment (UE) comprising: transmitting circuitry configured to:transmit a Radio Resource Control (RRC) message including firstinformation indicating a repetition type for a first configured grant(CG) Physical Uplink Shared Channel (PUSCH) transmission, transmit a RRCmessage including second information indicating a repetition type for asecond CG PUSCH transmission, transmit a RRC message including thirdinformation indicating whether codebook based transmission ornon-codebook based transmission is used for the first CG PUSCHtransmission and the second CG PUSCH transmission, receiving circuitryconfigured to: receive the first CG PUSCH transmission based on thefirst information and the third information, receive the second CG PUSCHtransmission based on the second information and the third information.

In one example, a communication method of a user equipment comprising:receiving a Radio Resource Control (RRC) message including firstinformation indicating a repetition type for a first configured grant(CG) Physical Uplink Shared Channel (PUSCH) transmission, receiving aRRC message including second information indicating a repetition typefor a second CG PUSCH transmission, receiving a RRC message includingthird information indicating whether codebook based transmission ornon-codebook based transmission is used for the first CG PUSCHtransmission and the second CG PUSCH transmission, performing the firstCG PUSCH transmission based on the first information and the thirdinformation, performing the second CG PUSCH transmission based on thesecond information and the third information.

In one example, a communication method of a base station apparatuscomprising: transmitting a Radio Resource Control (RRC) messageincluding first information indicating a repetition type for a firstconfigured grant (CG) Physical Uplink Shared Channel (PUSCH)transmission, transmitting a RRC message including second informationindicating a repetition type for a second CG PUSCH transmission,transmitting a RRC message including third information indicatingwhether codebook based transmission or non-codebook based transmissionis used for the first CG PUSCH transmission and the second CG PUSCHtransmission, receiving the first CG PUSCH transmission based on thefirst information and the third information, receiving the second CGPUSCH transmission based on the second information and the thirdinformation.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is a block diagram illustrating one implementation of one or morebase station apparatuses (gNBs) and one or more user equipments (UEs) inwhich systems and methods for signaling may be implemented.

FIG. 2 shows examples of multiple numerologies.

FIG. 3 is a diagram illustrating one example of a resource grid andresource block.

FIG. 4 shows examples of resource regions.

FIG. 5 illustrates an example of an UL transmission(s) corresponding toa configured grant(s).

FIG. 6 illustrates various components that may be utilized in a UE.

FIG. 7 illustrates various components that may be utilized in a gNB.

FIG. 8 is a block diagram illustrating one implementation of a UE inwhich one or more of the systems and/or methods described herein may beimplemented.

FIG. 9 is a block diagram illustrating one implementation of a gNB inwhich one or more of the systems and/or methods described herein may beimplemented.

FIG. 10 is a block diagram illustrating one implementation of a gNB.

FIG. 11 is a block diagram illustrating one implementation of a UE.

DESCRIPTION OF EMBODIMENTS

A user equipment (UE) is described. The UE includes receiving circuitryconfigured to receive a common configuration comprising parametersshared by multiple configured grants. The UE also includes transmittingcircuitry configured to perform, based on the parameters shared by themultiple configured grants of the common configuration, transmissions ona physical uplink shared channel (PUSCH).

In an approach, parameters in a specific configured grant may overwritethe parameters of the common configuration. In another approach, theparameters of the common configuration may overwrite parameters in aspecific configured grant.

The shared parameters may be included in a configuration for a primaryconfigured grant. A secondary configured grant may follow the sharedparameters included in the configuration for the primary configuredgrant.

A base station apparatus is also described. The base station apparatusincludes transmitting circuitry configured to transmit a commonconfiguration comprising parameters shared by multiple configuredgrants. The base station apparatus also includes receiving circuitryconfigured to receive, based on the parameters shared by the multipleconfigured grants of the common configuration, transmissions on a PUSCH.

A communication method of a UE is also described. The method includesreceiving a common configuration comprising parameters shared bymultiple configured grants. The method also includes performing, basedon the parameters shared by the multiple configured grants of the commonconfiguration, transmissions on a PUSCH.

A communication method of a base station apparatus is also described.The method includes transmitting a common configuration comprisingparameters shared by multiple configured grants. The method alsoincludes receiving, based on the parameters shared by the multipleconfigured grants of the common configuration, transmissions on a PUSCH.

The 3rd Generation Partnership Project, also referred to as “3GPP,” is acollaboration agreement that aims to define globally applicabletechnical specifications and technical reports for third and fourthgeneration wireless communication systems. The 3GPP may definespecifications for next generation mobile networks, systems and devices.

3GPP Long Term Evolution (LTE) is the name given to a project to improvethe Universal Mobile Telecommunications System (UMTS) mobile phone ordevice standard to cope with future requirements. In one aspect, UMTShas been modified to provide support and specification for the EvolvedUniversal Terrestrial Radio Access (E-UTRA) and Evolved UniversalTerrestrial Radio Access Network (E-UTRAN).

At least some aspects of the systems and methods disclosed herein may bedescribed in relation to the 3GPP LTE, LTE-Advanced (LTE-A) and otherstandards (e.g., 3GPP Releases 8, 9, 10, 11, 12, 13, 14 and/or 15).However, the scope of the present disclosure should not be limited inthis regard. At least some aspects of the systems and methods disclosedherein may be utilized in other types of wireless communication systems.

A wireless communication device may be an electronic device used tocommunicate voice and/or data to a base station, which in turn maycommunicate with a network of devices (e.g., public switched telephonenetwork (PSTN), the Internet, etc.). In describing systems and methodsherein, a wireless communication device may alternatively be referred toas a mobile station, a UE, an access terminal, a subscriber station, amobile terminal, a remote station, a user terminal, a terminal, asubscriber unit, a mobile device, etc. Examples of wirelesscommunication devices include cellular phones, smart phones, personaldigital assistants (PDAs), laptop computers, netbooks, e-readers,wireless modems, etc. In 3GPP specifications, a wireless communicationdevice is typically referred to as a UE. However, as the scope of thepresent disclosure should not be limited to the 3GPP standards, theterms “UE” and “wireless communication device” may be usedinterchangeably herein to mean the more general term “wirelesscommunication device.” A UE may also be more generally referred to as aterminal device.

In 3GPP specifications, a base station is typically referred to as aNode B, an evolved Node B (eNB), a home enhanced or evolved Node B(HeNB) or some other similar terminology. As the scope of the disclosureshould not be limited to 3GPP standards, the terms “base station,” “NodeB,” “eNB,” “gNB” and “HeNB” may be used interchangeably herein to meanthe more general term “base station.” Furthermore, the term “basestation” may be used to denote an access point. An access point may bean electronic device that provides access to a network (e.g., Local AreaNetwork (LAN), the Internet, etc.) for wireless communication devices.The term “communication device” may be used to denote both a wirelesscommunication device and/or a base station. An eNB may also be moregenerally referred to as a base station device.

It should be noted that as used herein, a “cell” may be anycommunication channel that is specified by standardization or regulatorybodies to be used for International Mobile Telecommunications-Advanced(IMT-Advanced) and all of it or a subset of it may be adopted by 3GPP aslicensed bands (e.g., frequency bands) to be used for communicationbetween an eNB and a UE. It should also be noted that in E-UTRA andE-UTRAN overall description, as used herein, a “cell” may be defined(e.g., specified) as a “combination of downlink and optionally uplinkresources.” The linking between the carrier frequency of the downlinkresources and the carrier frequency of the uplink resources may beindicated in the system information transmitted on the downlinkresources.

The 5th generation communication systems, dubbed NR (New Radiotechnologies) by 3GPP, envision the use of time, frequency, and/or spaceresources to allow for services, such as eMBB (enhanced MobileBroad-Band) transmission, URLLC (Ultra Reliable and Low LatencyCommunication) transmission, and eMTC (massive Machine TypeCommunication) transmission. And, in NR, transmissions for differentservices may be specified (e.g., configured) for one or more bandwidthparts (BWPs) in a serving cell and/or for one or more serving cells. Auser equipment (UE) may receive a downlink signal(s) and/or transmit anuplink signal(s) in the BWP(s) of the serving cell and/or the servingcell(s).

In order for the services to use the time, frequency, and/or spaceresources efficiently, it would be useful to be able to efficientlycontrol downlink and/or uplink transmissions. Therefore, a procedure forefficient control of downlink and/or uplink transmissions should bedesigned. Accordingly, a detailed design of a procedure for downlinkand/or uplink transmissions may be beneficial.

Various examples of the systems and methods disclosed herein are nowdescribed with reference to the Figures, where like reference numbersmay indicate functionally similar elements. The systems and methods asgenerally described and illustrated in the Figures herein could bearranged and designed in a wide variety of different implementations.Thus, the following more detailed description of severalimplementations, as represented in the Figures, is not intended to limitscope, as claimed, but is merely representative of the systems andmethods.

FIG. 1 is a block diagram illustrating one implementation of one or moregNBs 160 and one or more UEs 102 in which systems and methods forsignaling may be implemented. The one or more UEs 102 communicate withone or more gNBs 160 using one or more physical antennas 122 a-n. Forexample, a UE 102 transmits electromagnetic signals to the gNB 160 andreceives electromagnetic signals from the gNB 160 using the one or morephysical antennas 122 a-n. The gNB 160 communicates with the UE 102using one or more physical antennas 180 a-n. In some implementations,the term “base station,” “eNB,” and/or “gNB” may refer to and/or may bereplaced by the term “Transmission Reception Point (TRP).” For example,the gNB 160 described in connection with FIG. 1 may be a TRP in someimplementations.

The UE 102 and the gNB 160 may use one or more channels and/or one ormore signals 119, 121 to communicate with each other. For example, theUE 102 may transmit information or data to the gNB 160 using one or moreuplink channels 121. Examples of uplink channels 121 include a physicalshared channel (e.g., PUSCH (physical uplink shared channel)) and/or aphysical control channel (e.g., PUCCH (physical uplink controlchannel)), etc. The one or more gNBs 160 may also transmit informationor data to the one or more UEs 102 using one or more downlink channels119, for instance. Examples of downlink channels 119 include a physicalshared channel (e.g., PDCCH (physical downlink shared channel) and/or aphysical control channel (PDCCH (physical downlink control channel)),etc. Other kinds of channels and/or signals may be used.

Each of the one or more UEs 102 may include one or more transceivers118, one or more demodulators 114, one or more decoders 108, one or moreencoders 150, one or more modulators 154, a data buffer 104 and a UEoperations module 124. For example, one or more reception and/ortransmission paths may be implemented in the UE 102. For convenience,only a single transceiver 118, decoder 108, demodulator 114, encoder 150and modulator 154 are illustrated in the UE 102, though multipleparallel elements (e.g., transceivers 118, decoders 108, demodulators114, encoders 150 and modulators 154) may be implemented.

The transceiver 118 may include one or more receivers 120 and one ormore transmitters 158. The one or more receivers 120 may receive signalsfrom the gNB 160 using one or more antennas 122 a-n. For example, thereceiver 120 may receive and downconvert signals to produce one or morereceived signals 116. The one or more received signals 116 may beprovided to a demodulator 114. The one or more transmitters 158 maytransmit signals to the gNB 160 using one or more physical antennas 122a-n. For example, the one or more transmitters 158 may upconvert andtransmit one or more modulated signals 156.

The demodulator 114 may demodulate the one or more received signals 116to produce one or more demodulated signals 112. The one or moredemodulated signals 112 may be provided to the decoder 108. The UE 102may use the decoder 108 to decode signals. The decoder 108 may producedecoded signals 110, which may include a UE-decoded signal 106 (alsoreferred to as a first UE-decoded signal 106). For example, the firstUE-decoded signal 106 may include received payload data, which may bestored in a data buffer 104. Another signal included in the decodedsignals 110 (also referred to as a second UE-decoded signal 110) mayinclude overhead data and/or control data. For example, the second UEdecoded signal 110 may provide data that may be used by the UEoperations module 124 to perform one or more operations.

In general, the UE operations module 124 may enable the UE 102 tocommunicate with the one or more gNBs 160. The UE operations module 124may include one or more of a UE scheduling module 126.

The UE scheduling module 126 may perform downlink reception(s) anduplink transmission(s). The downlink reception(s) include reception ofdata, reception of downlink control information, and/or reception ofdownlink reference signals. Also, the uplink transmissions includetransmission of data, transmission of uplink control information, and/ortransmission of uplink reference signals.

In a radio communication system, physical channels (uplink physicalchannels and/or downlink physical channels) may be defined. The physicalchannels (uplink physical channels and/or downlink physical channels)may be used for transmitting information that is delivered from a higherlayer.

For example, in uplink, a PRACH (Physical Random Access Channel) may bedefined. In some approaches, the PRACH (e.g., the random accessprocedure) may be used for an initial access connection establishmentprocedure, a handover procedure, a connection re-establishment, a timingadjustment (e.g., a synchronization for an uplink transmission, for ULsynchronization) and/or for requesting an uplink shared channel (UL-SCH)resource (e.g., the uplink physical shared channel (PSCH) (e.g., PUCCH)resource).

In another example, a physical uplink control channel (PUCCH) may bedefined. The PUCCH may be used for transmitting uplink controlinformation (UCI). The UCI may include hybrid automatic repeatrequest-acknowledgement (HARQ-ACK), channel state information (CSI)and/or a scheduling request (SR). The HARQ-ACK is used for indicating apositive acknowledgement (ACK) or a negative acknowledgment (NACK) fordownlink data (e.g., Transport block(s), Medium Access Control ProtocolData Unit (MAC PDU) and/or Downlink Shared Channel (DL-SCH)). The CSI isused for indicating state of downlink channel (e.g., a downlinksignal(s)). Also, the SR is used for requesting resources of uplink data(e.g., Transport block(s), MAC PDU and/or Uplink Shared Channel(UL-SCH)).

Here, the DL-SCH and/or the UL-SCH may be a transport channel that isused in the MAC layer. Also, a transport block(s) (TB(s)) and/or a MACPDU may be defined as a unit(s) of the transport channel used in the MAClayer. The transport block may be defined as a unit of data deliveredfrom the MAC layer to the physical layer. The MAC layer may deliver thetransport block to the physical layer (e.g., the MAC layer delivers thedata as the transport block to the physical layer). In the physicallayer, the transport block may be mapped to one or more codewords.

In downlink, a physical downlink control channel (PDCCH) may be defined.The PDCCH may be used for transmitting downlink control information(DCI). Here, more than one DCI formats may be defined for DCItransmission on the PDCCH. Namely, fields may be defined in the DCIformat(s), and the fields are mapped to the information bits (e.g., DCIbits).

For example, a DCI format 1_0 that is used for scheduling of the PDSCHin the cell may be defined as the DCI format for the downlink. Also, asdescribed herein one or more Radio Network Temporary Identifiers (e.g.,the Cell RNTI(s) (C-RNTI(s)), the Configured Scheduling RNTI(s)(CS-RNTI(s)), the System Information RNTI(s) (SI-RNTI(s)), and/or theRandom Access RNTI(s) (RA-RNTI(s)) may be used to transmit the DCIformat 1_0. Also, the DCI format 1_0 may be monitored (e.g.,transmitted, mapped) in the Common Search Space (CSS) and/or the UESpecific Search space (USS). Alternatively, the DCI format 1_0 may bemonitored (e.g., transmitted, mapped) in the CSS only.

For example, the DCI included in the DCI format 1_0 may be a frequencydomain resource assignment (e.g., for the PDSCH). Additionally oralternatively, the DCI included in the DCI format 1_0 may be a timedomain resource assignment (e.g., for the PDSCH). Additionally oralternatively, the DCI included in the DCI format 1_0 may be amodulation and coding scheme (e.g., for the PDSCH). Additionally oralternatively, or alternatively, the DCI included in the DCI format 1_0may be a new data indicator. Additionally or alternatively, the DCIincluded in the DCI format 1_0 may be a TPC (e.g., Transmission PowerControl) command for scheduled PUCCH.

Additionally or alternatively, a DCI format 1_1 that is used forscheduling of the PDSCH in the cell may be defined as the DCI format forthe downlink. Additionally or alternatively, the C-RNTI, the CS-RNTI maybe used to transmit the DCI format 1_1. Additionally or alternatively,the DCI format 1_1 may be monitored (e.g., transmitted and/or mapped) inthe CSS and/or the USS.

For example, the DCI included in the DCI format 1_1 may be a BWPindicator (e.g., for the PDSCH). Additionally or alternatively, the DCIincluded in the DCI format 1_1 may be frequency domain resourceassignment (e.g., for the PDSCH). Additionally or alternatively, the DCIincluded in the DCI format 1_1 may be a time domain resource assignment(e.g., for the PDSCH). Additionally or alternatively, the DCI includedin the DCI format 1_1 may be a modulation and coding scheme (e.g., forthe PDSCH). Additionally or alternatively, the DCI included in the DCIformat 1_1 may be a new data indicator. Additionally or alternatively,the DCI included in the DCI format 1_1 may be a TPC command forscheduled PUCCH. Additionally or alternatively, the DCI included in theDCI format 1_1 may be a CSI request that is used for requesting (e.g.,triggering) transmission of the CSI (e.g., CSI reporting (e.g.,aperiodic CSI reporting)).

Additionally or alternatively, a DCI format 0_0 that is used forscheduling of the PUSCH in the cell may be defined as the DCI format forthe uplink. Additionally or alternatively, the C-RNTI, the CS-RNTI,and/or the Temporary C-RNTI may be used to transmit the DCI format 0_0.Additionally or alternatively, the DCI format 0_0 may be monitored(e.g., transmitted, mapped) in the CSS and/or the USS. Alternatively,the DCI format 0_0 may be monitored (e.g., transmitted, mapped) in theCSS only.

For example, the DCI included in the DCI format 0_0 may be a frequencydomain resource assignment (e.g., for the PUSCH). Additionally oralternatively, the DCI included in the DCI format 0_0 may be a timedomain resource assignment (e.g., for the PUSCH). Additionally oralternatively, the DCI included in the DCI format 0_0 may be amodulation and coding scheme (e.g., for the PUSCH). Additionally oralternatively, the DCI included in the DCI format 0_0 may be a new dataindicator. Additionally or alternatively, the DCI included in the DCIformat 0_0 may be a redundancy version. Additionally or alternatively,the DCI included in the DCI format 0_0 may be a TPC command forscheduled PUSCH.

Additionally or alternatively, a DCI format 0_1 that is used forscheduling of the PUSCH in the cell may be defined as the DCI format forthe uplink. Additionally or alternatively, the C-RNTI, the CS-RNTI maybe used to transmit the DCI format 0_1. Additionally or alternatively,the DCI format 0_1 may be monitored (e.g., transmitted, mapped) in theCSS and/or the USS.

For example, the DCI included in the DCI format 0_1 may be a BWPindicator (e.g., for the PUSCH). Additionally or alternatively, the DCIincluded in the DCI format 0_1 may be a frequency domain resourceassignment (e.g., for the PUSCH). Additionally or alternatively, the DCIincluded in the DCI format 0_1 may be a time domain resource assignment(e.g., for the PUSCH). Additionally or alternatively, the DCI includedin the DCI format 0_1 may be a modulation and coding scheme (e.g., forthe PUSCH). Additionally or alternatively, the DCI included in the DCIformat 0_1 may be a new data indicator. Additionally or alternatively,the DCI included in the DCI format 0_1 may be a TPC command forscheduled PUSCH. Additionally or alternatively, the DCI included in theDCI format 0_1 may be a CSI request that is used for requesting the CSIreporting. Additionally or alternatively, as described below, the DCIincluded in the DCI format 0_1 may be information used for indicating anindex of a configuration of a configured grant.

Additionally or alternatively, in a case that the DCI format 1_0 and/orthe DCI format 1_1 is received (e.g., based on the detection of the DCIformat 1_0 and/or the DCI format 1_1), the UE 102 may perform the PDSCHreception. Additionally or alternatively, in a case that the DCI format0_0 and/or the DCI format 0_1 is received (e.g., based on the detectionof the DCI format 0_0 and/or the DCI format 0_1), the UE 102 may performthe PUSCH transmission.

Here, as described above, a RNTI(s) (e.g., a Radio Network TemporaryIdentifier(s)) assigned to the UE 102 may be used for transmission ofDCI (e.g., the DCI format(s), DL control channel(s) (e.g., thePDCCH(s)). Namely, the gNB 160 may transmit, (e.g., by using the RRCmessage), information used for configuring (e.g., assigning) the RNTI(s)to the UE 102.

For example, CRC (Cyclic Redundancy Check) parity bits (also referred tosimply as CRC), which are generated based on DCI, are attached to DCI,and, after attachment, the CRC parity bits are scrambled by the RNTI(s).The UE 102 may attempt to decode (e.g., blind decoding, monitor, detect)DCI to which the CRC parity bits scrambled by the RNTI(s) are attached.For example, the UE 102 detects DL control channel (e.g., the PDCCH, theDCI, the DCI format(s)) based on the blind decoding. That is, the UE 102may decode the DL control channel(s) with the CRC scrambled by theRNTI(s). In other words, the UE 102 may monitor the DL controlchannel(s) with the RNTI(s). For example, the UE 102 may detect the DCIformat(s) with the RNTI(s).

Here, the RNTI(s) may include the C-RNTI(s) (Cell-RNTI(s)), theCS-RNTI(s) (Configured Scheduling C-RNTI(s)), the SI-RNTI(s) (SystemInformation RNTI(s)), the RA-RNTI(s) (Random Access-RNTI(s)), and/or theTemporary C-RNTI(s).

For example, the C-RNTI(s) may be a unique identification used foridentifying a RRC connection and/or scheduling. Additionally oralternatively, the CS-RNTI(s) may be a unique identification used forscheduling of transmission based on a configured grant. Additionally oralternatively, the SI-RNTI may be used for identifying systeminformation (SI) (e.g., an SI message) mapped on the BCCH anddynamically carried on DL-SCH. Additionally or alternatively, theSI-RNTI may be used for broadcasting of SI. Additionally oralternatively, the RA-RNTI may be an identification used for the randomaccess procedure (e.g., Msg.2 transmission). Additionally oralternatively, the Temporary C-RNTI may be used for the random accessprocedure (e.g., scheduling of Msg.3 (re)transmission (e.g., Msg.3 PUSCH(re)transmission)).

Additionally or alternatively, a physical downlink shared channel(PDSCH) and a physical uplink shared channel (PUSCH) may be defined. Forexample, in a case that the PDSCH (e.g., the PDSCH resource) isscheduled by using the DCI format(s), the UE 102 may receive thedownlink data, on the scheduled PDSCH (e.g., the PDSCH resource).Additionally or alternatively, in a case that the PUSCH (e.g., the PUSCHresource) is scheduled by using the DCI format(s), the UE 102 transmitsthe uplink data, on the scheduled PUSCH (e.g., the PUSCH resource). Forexample, the PDSCH may be used to transmit the downlink data (e.g.,DL-SCH(s), a downlink transport block(s)). Additionally oralternatively, the PUSCH may be used to transmit the uplink data (e.g.,UL-SCH(s), an uplink transport block(s)).

Furthermore, the PDSCH and/or the PUSCH may be used to transmitinformation of a higher layer (e.g., a radio resource control (RRC))layer, and/or a MAC layer). For example, the PDSCH (e.g., from the gNB160 to the UE 102) and/or the PUSCH (e.g., from the UE 102 to the gNB160) may be used to transmit a RRC message (a RRC signal). Additionallyor alternatively, the PDSCH (e.g., from the gNB 160 to the UE 102)and/or the PUSCH (e.g., from the UE 102 to the gNB 160) may be used totransmit a MAC control element (a MAC CE). Here, the RRC message and/orthe MAC CE are also referred to as a higher layer signal.

In some approaches, a physical broadcast channel (PBCH) may be defined.For example, the PBCH may be used for broadcasting the MIB (masterinformation block). Here, system information may be divided into the MIBand a number of SIB(s) (system information block(s)). For example, theMIB may be used for carrying include minimum system information.Additionally or alternatively, the SIB(s) may be used for carryingsystem information messages.

In some approaches, in downlink, a SS (Synchronization Signal) may bedefined. The SS may be used for acquiring time and/or frequencysynchronization with a cell. Additionally or alternatively, the SS maybe used for detecting a physical layer cell ID of the cell.

In the radio communication for uplink, UL RS(s) may be used as uplinkphysical signal(s). Additionally or alternatively, in the radiocommunication for downlink, DL RS(s) may be used as downlink physicalsignal(s). The uplink physical signal(s) and/or the downlink physicalsignal(s) may not be used to transmit information that is provided fromthe higher layer, but is used by a physical layer.

Here, the downlink physical channel(s) and/or the downlink physicalsignal(s) described herein may be assumed to be included in a downlinksignal (e.g., a DL signal(s)) in some implementations for the sake ofsimple descriptions. Additionally or alternatively, the uplink physicalchannel(s) and/or the uplink physical signal(s) described herein may beassumed to be included in an uplink signal (i.e. an UL signal(s)) insome implementations for the sake of simple descriptions.

The UE operations module 124 may provide information 148 to the one ormore receivers 120. For example, the UE operations module 124 may informthe receiver(s) 120 when to receive retransmissions.

The UE operations module 124 may provide information 138 to thedemodulator 114. For example, the UE operations module 124 may informthe demodulator 114 of a modulation pattern anticipated fortransmissions from the gNB 160.

The UE operations module 124 may provide information 136 to the decoder108. For example, the UE operations module 124 may inform the decoder108 of an anticipated encoding for transmissions from the gNB 160.

The UE operations module 124 may provide information 142 to the encoder150. The information 142 may include data to be encoded and/orinstructions for encoding. For example, the UE operations module 124 mayinstruct the encoder 150 to encode transmission data 146 and/or otherinformation 142. The other information 142 may include PDSCH HARQ-ACKinformation.

The encoder 150 may encode transmission data 146 and/or otherinformation 142 provided by the UE operations module 124. For example,encoding the data 146 and/or other information 142 may involve errordetection and/or correction coding, mapping data to space, time and/orfrequency resources for transmission, multiplexing, etc. The encoder 150may provide encoded data 152 to the modulator 154.

The UE operations module 124 may provide information 144 to themodulator 154. For example, the UE operations module 124 may inform themodulator 154 of a modulation type (e.g., constellation mapping) to beused for transmissions to the gNB 160. The modulator 154 may modulatethe encoded data 152 to provide one or more modulated signals 156 to theone or more transmitters 158.

The UE operations module 124 may provide information 140 to the one ormore transmitters 158. This information 140 may include instructions forthe one or more transmitters 158. For example, the UE operations module124 may instruct the one or more transmitters 158 when to transmit asignal to the gNB 160. For instance, the one or more transmitters 158may transmit during a UL subframe. The one or more transmitters 158 mayupconvert and transmit the modulated signal(s) 156 to one or more gNBs160.

Each of the one or more gNBs 160 may include one or more transceivers176, one or more demodulators 172, one or more decoders 166, one or moreencoders 109, one or more modulators 113, a data buffer 162 and a gNBoperations module 182. For example, one or more reception and/ortransmission paths may be implemented in a gNB 160. For convenience,only a single transceiver 176, decoder 166, demodulator 172, encoder 109and modulator 113 are illustrated in the gNB 160, though multipleparallel elements (e.g., transceivers 176, decoders 166, demodulators172, encoders 109 and modulators 113) may be implemented.

The transceiver 176 may include one or more receivers 178 and one ormore transmitters 117. The one or more receivers 178 may receive signalsfrom the UE 102 using one or more physical antennas 180 a-n. Forexample, the receiver 178 may receive and downconvert signals to produceone or more received signals 174. The one or more received signals 174may be provided to a demodulator 172. The one or more transmitters 117may transmit signals to the UE 102 using one or more physical antennas180 a-n. For example, the one or more transmitters 117 may upconvert andtransmit one or more modulated signals 115.

The demodulator 172 may demodulate the one or more received signals 174to produce one or more demodulated signals 170. The one or moredemodulated signals 170 may be provided to the decoder 166. The gNB 160may use the decoder 166 to decode signals. The decoder 166 may produceone or more decoded signals 164, 168. For example, a first eNB-decodedsignal 164 may include received payload data, which may be stored in adata buffer 162. A second eNB-decoded signal 168 may include overheaddata and/or control data. For example, the second eNB decoded signal 168may provide data (e.g., PDSCH HARQ-ACK information) that may be used bythe gNB operations module 182 to perform one or more operations.

In general, the gNB operations module 182 may enable the gNB 160 tocommunicate with the one or more UEs 102. The gNB operations module 182may include one or more of a gNB scheduling module 194. The gNBscheduling module 194 may perform scheduling of downlink and/or uplinktransmissions as described herein.

The gNB operations module 182 may provide information 188 to thedemodulator 172. For example, the gNB operations module 182 may informthe demodulator 172 of a modulation pattern anticipated fortransmissions from the UE(s) 102.

The gNB operations module 182 may provide information 186 to the decoder166. For example, the gNB operations module 182 may inform the decoder166 of an anticipated encoding for transmissions from the UE(s) 102.

The gNB operations module 182 may provide information 101 to the encoder109. The information 101 may include data to be encoded and/orinstructions for encoding. For example, the gNB operations module 182may instruct the encoder 109 to encode information 101, includingtransmission data 105.

The encoder 109 may encode transmission data 105 and/or otherinformation included in the information 101 provided by the gNBoperations module 182. For example, encoding the data 105 and/or otherinformation included in the information 101 may involve error detectionand/or correction coding, mapping data to space, time and/or frequencyresources for transmission, multiplexing, etc. The encoder 109 mayprovide encoded data 111 to the modulator 113. The transmission data 105may include network data to be relayed to the UE 102.

The gNB operations module 182 may provide information 103 to themodulator 113. This information 103 may include instructions for themodulator 113. For example, the gNB operations module 182 may inform themodulator 113 of a modulation type (e.g., constellation mapping) to beused for transmissions to the UE(s) 102. The modulator 113 may modulatethe encoded data 111 to provide one or more modulated signals 115 to theone or more transmitters 117.

The gNB operations module 182 may provide information 192 to the one ormore transmitters 117. This information 192 may include instructions forthe one or more transmitters 117. For example, the gNB operations module182 may instruct the one or more transmitters 117 when to (or when notto) transmit a signal to the UE(s) 102. The one or more transmitters 117may upconvert and transmit the modulated signal(s) 115 to one or moreUEs 102.

It should be noted that a DL subframe may be transmitted from the gNB160 to one or more UEs 102 and that a UL subframe may be transmittedfrom one or more UEs 102 to the gNB 160. Furthermore, both the gNB 160and the one or more UEs 102 may transmit data in a standard specialsubframe.

It should also be noted that one or more of the elements or partsthereof included in the eNB(s) 160 and UE(s) 102 may be implemented inhardware. For example, one or more of these elements or parts thereofmay be implemented as a chip, circuitry or hardware components, etc. Itshould also be noted that one or more of the functions or methodsdescribed herein may be implemented in and/or performed using hardware.For example, one or more of the methods described herein may beimplemented in and/or realized using a chipset, an application-specificintegrated circuit (ASIC), a large-scale integrated circuit (LSI) orintegrated circuit, etc.

FIG. 2 shows examples of multiple numerologies 201. As shown in FIG. 2,multiple numerologies 201 (e.g., multiple subcarrier spacing) may besupported. For example, μ (e.g., a subcarrier space configuration) and acyclic prefix (e.g., the μ and the cyclic prefix for a carrier bandwidthpart) may be configured by higher layer parameters (e.g., a RRC message)for the downlink and/or the uplink. Here, 15 kHz may be a referencenumerology 201. For example, an RE of the reference numerology 201 maybe defined with a subcarrier spacing of 15 kHz in a frequency domain and2048 Ts+CP length (e.g. 160 Ts or 144 Ts) in a time domain, where Tsdenotes a baseband sampling time unit defined as 1/(15000*2048) seconds.

Additionally or alternatively, a number of OFDM symbol(s) 203 per slot(N_(symb) ^(slot)) may be determined based on the p (e.g., thesubcarrier space configuration). Here, for example, a slot configuration0 (e.g., the number of OFDM symbols 203 per slot may be 14) and/or aslot configuration (e.g., the number of OFDM symbols 203 per slot may be7) may be defined.

FIG. 3 is a diagram illustrating one example of a resource grid 301 andresource block 391 (e.g., for the downlink and/or the uplink). Theresource grid 301 and resource block 391 illustrated in FIG. 3 may beutilized in some implementations of the systems and methods disclosedherein.

In FIG. 3, one subframe 369 may include N_(symbol) ^(subframe,μ) symbols387. Additionally or alternatively, a resource block 391 may include anumber of resource elements (RE) 389. Here, in the downlink, the OFDMaccess scheme with cyclic prefix (CP) may be employed, which may be alsoreferred to as CP-OFDM. A downlink radio frame may include multiplepairs of downlink resource blocks (RBs) 391 which are also referred toas physical resource blocks (PRBs). The downlink RB pair is a unit forassigning downlink radio resources, defined by a predetermined bandwidth(RB bandwidth) and a time slot. The downlink RB pair may include twodownlink RBs 391 that are continuous in the time domain. Additionally oralternatively, the downlink RB 391 may include twelve sub-carriers infrequency domain and seven (for normal CP) or six (for extended CP) OFDMsymbols in time domain. A region defined by one sub-carrier in frequencydomain and one OFDM symbol in time domain is referred to as a resourceelement (RE) 389 and is uniquely identified by the index pair (k,l),where k and l are indices in the frequency and time domains,respectively.

Additionally or alternatively, in the uplink, in addition to CP-OFDM, aSingleCarrier Frequency Division Multiple Access (SC-FDMA) access schememay be employed, which is also referred to as Discrete FourierTransform-Spreading OFDM (DFT-S-OFDM). An uplink radio frame may includemultiple pairs of uplink resource blocks 391. The uplink RB pair is aunit for assigning uplink radio resources, defined by a predeterminedbandwidth (RB bandwidth) and a time slot. The uplink RB pair may includetwo uplink RBs 391 that are continuous in the time domain. The uplink RBmay include twelve sub-carriers in frequency domain and seven (fornormal CP) or six (for extended CP) OFDM/DFT-S-OFDM symbols in timedomain. A region defined by one sub-carrier in the frequency domain andone OFDM/DFT-S-OFDM symbol in the time domain is referred to as aresource element (RE) 389 and is uniquely identified by the index pair(k,l) in a slot, where k and l are indices in the frequency and timedomains respectively.

Each element in the resource grid 301 (e.g., antenna port p) and thesubcarrier configuration μ is called a resource element 389 and isuniquely identified by the index pair (k,l) where k=0, N_(RB) ^(μ)N_(SC)^(RB)−1 is the index in the frequency domain and l refers to the symbolposition in the time domain. The resource element (k,l) 389 on theantenna port p and the subcarrier spacing configuration μ is denoted(k,l)_(p),μ. The physical resource block 391 is defined as N_(SC)^(RB)=12 consecutive subcarriers in the frequency domain. The physicalresource blocks 391 are numbered from 0 to N_(RB) ^(μ)−1 in thefrequency domain. The relation between the physical resource blocknumber n_(PRB) in the frequency domain and the resource element (k,l) isgiven by

${\,^{n}{PRB}} = {\left\lfloor \frac{k}{N_{SC}^{RB}} \right\rfloor.}$

FIG. 4 shows examples of resource regions (e.g., resource region of thedownlink). One or more sets 401 of PRB(s) 491 (e.g., a control resourceset (e.g., CORESET)) may be configured for DL control channel monitoring(e.g., the PDCCH monitoring). For example, the CORESET is, in thefrequency domain and/or the time domain, a set 401 of PRBs 491 withinwhich the UE 102 attempts to decode the DCI (e.g., the DCI format(s),the PDCCH(s)), where the PRBs 491 may or may not be frequency contiguousand/or time contiguous, a UE 102 may be configured with one or morecontrol resource sets (e.g., the CORESETs) and one DCI message may bemapped within one control resource set. In the frequency-domain, a PRB491 is the resource unit size (which may or may not include DM-RS) forthe DL control channel.

The UE 102 may monitor a set of candidates of the PDCCH in one or morecontrol resource sets (e.g., CORESETs) on the active DL bandwidth part(BWP) on each activated serving cell according to corresponding searchspace sets. Here, the term “monitor” may imply that the UE 102 attemptsto decode each PDCCH (e.g., the set of candidates of the PDCCH)according to the monitored DCI format(s). Also, the candidates of thePDCCH may be candidates for which the DL control channel(s) may possiblybe mapped, assigned, and/or transmitted.

The set of candidates of the PDCCH for the UE 102 to monitor may bedefined in terms of a search space set(s) (e.g., also referred to simplyas a search space(s)). The UE 102 may monitor the set of candidates ofthe PDCCH in the search space(s). The search space set(s) may include acommon search space(s) (CSS(s), UE-common search space(s)) and/or a userequipment-specific search space(s) (USS, UE-specific search space(s)).

Namely, the CSS and/or the USS may be defined (e.g., configured) in aregion(s) of DL control channel(s). For example, the CSS may be used fortransmission of DCI to a plurality of the UEs 102. For example, aType0-PDCCH common search space may be defined for the DCI format(s)with CRC scrambled by the SI-RNTI. Additionally or alternatively, aType1-PDCCH common search space may be defined for the DCI format(s)with CRC scrambled by the RA-RNTI, the Temporary C-RNTI, and/or theC-RNTI. Additionally or alternatively, a Type3-PDCCH common search spacemay be defined for the DCI format(s) with CRC scrambled by the C-RNTI,and/or the CS-RNTI.

The USS may be used for transmission of DCI to a specific UE 102. Forexample, the USS may be determined based on a Radio Network TemporaryIdentifier (RNTI) (e.g., the C-RNTI). For instance, the USS may bedefined for the DCI format(s) with CRC scrambled by the C-RNTI, and/orthe CS-RNTI.

Here, the gNB 160 may transmit, by using the RRC message, firstinformation used for configuring (e.g., determining) one or moreCORESETs. For example, for each of DL BWPs (e.g., each of DL BWPs in theserving cell), the gNB 106 may transmit, by using the RRC message, thefirst information used for configuring the one or more CORESET. Forexample, the first information may include information used forconfiguring an index of the CORESET. Also, the first information mayinclude information used for configuring a number of consecutive symbolsfor the CORESET. Also, the first information may include informationused for configuring a set of resource blocks for the CORESET.

Additionally or alternatively, the gNB 160 may transmit, by using theRRC message, second information used for configuring the search spaceset(s). For example, the second information may be configured for eachsearch space set. For example, the second information may includeinformation used for configuring an index of the search space set(s).Additionally or alternatively, the second information may includeinformation used for configuring the index of the CORESET(s) associatedwith the search space set(s). Additionally or alternatively, the secondinformation may include information used for indicating a PDCCHmonitoring periodicity and/or a PDCCH monitoring offset where the UE 102monitors the PDCCH(s) in the search space set(s). Additionally oralternatively, the second information may include information used forindicating a PDCCH monitoring pattern within a slot. For example, theinformation used for indicating the PDCCH monitoring pattern may be usedfor indicating first symbol(s) within a slot for the PDCCH monitoring.For instance, the UE 102 may determine a PDCCH monitoring occasion(s)based on the PDCCH monitoring periodicity, the PDCCH monitoring offset,and/or the PDCCH monitoring pattern within a slot.

Additionally or alternatively, the second information may includeinformation used for indicating a type of the search space set (e.g.,information used for indicating that the search space set is either theCSS or the USS). Additionally or alternatively, the second informationmay include information used for indicating one or more DCI formatswhich accordingly the UE 102 monitors the PDCCH in the search spaceset(s). For example, if the search space set is the CSS (e.g., if thesearch space set is configured as the CSS), the DCI format 0_0 and/orthe DCI format 1_0 may be configured to monitor the PDCCH (e.g., thecandidate(s) of the PDCCH(s)). Here, the DCI format(s) for monitoringthe PDCCH in the CSS may be scrambled by the C-RNTI, the CS-RNTI, theRA-RNTI, the Temporary C-RNTI, and/or the SI-RNTI.

Additionally or alternatively, if the search space set is the USS (e.g.,if the search space set is configured as the USS), the DCI format 0_0and/or the DCI format 1_0 may be configured to monitor the PDCCH (e.g.,the candidate(s) of the PDCCH(s)). Additionally or alternatively, if thesearch space set is the USS, the DCI format 0_1 and/or the DCI format1_1 may be configured to monitor the PDCCH (e.g., the candidate(s) ofthe PDCCH(s)). For example, if the search space set is the USS, eitherof a first set of DCI formats (e.g., the DCI format 0_0 and/or the DCIformat 1_0) or a second set of DCI formats (e.g., the DCI format 0_1and/or the DCI format 1_1) may be configured to monitor the PDCCH (e.g.,the candidate(s) of the PDCCH(s)). Here, the DCI format(s) formonitoring the PDCCH in the USS may be scrambled by the C-RNTI, theCS-RNTI. For example, the second information may be configured persearch space set. Namely, the second information may be configured foreach of search space sets.

Here, for example, for the serving cell(s), the gNB 160 may configure,by using the RRC message, a set of four DL BWPs (e.g., at most four DLBWPs, a DL BWP set) (e.g., for receptions by the UE 102). Additionallyor alternatively, the gNB 160 may indicate, by using the DCI format(s)for the downlink, an active DL BWP(s). For example, for each DL BWP inthe set of DL BWPs, the gNB 160 may configure, by using the RRC message,the subcarrier spacing, the cyclic prefix, a number of contiguous PRBs491 (e.g., a bandwidth of PRBs), and/or an index (e.g., the index of theDL BWP(s)) in the set of DL BWPs.

Additionally or alternatively, for the serving cell(s), the gNB 160 mayconfigure, by using the RRC message, a set of four UL BWP(s) (e.g., atmost four UL BWPs, a UL BWP set) (e.g., for transmissions by the UE102). Additionally or alternatively, the gNB 160 may indicate, by usingthe DCI format(s) for the uplink, an active UL BWP(s). Additionally oralternatively, for each UL BWP in the set of UL BWPs, the gNB 160 mayconfigure, by using the RRC message, the subcarrier spacing, the cyclicprefix, a number of contiguous PRBs 491 (e.g., a bandwidth of PRBs), anindex (e.g., the index of the UL BWP(s)) in the set of UL BWPs.

Additionally or alternatively, the UE 102 may perform, based on theconfiguration(s) for the DL BWP(s), reception(s) on the PDCCH in the DLBWP(s) and/or reception(s) on the PDSCH in the DL BWP(s). Additionallyor alternatively, the UE 102 may perform, based on the configuration(s)for the UL BWP(s).

FIG. 5 illustrates an example of an UL transmission(s) corresponding toa configured grant(s). As described as FIG. 5, the UE 102 may performthe UL transmission(s) (e.g., the (re)transmission(s) on the UL-SCH,and/or the (re)transmission(s) on the PUSCH 503 a-d). For example, theUE 102 may perform the UL transmission(s) on the PUSCH 503 a-d on the ULBWP(s) in the serving cell. Here, the DL BWP(s) and the UL BWP(s) islinked in a case that the index of the DL BWP and the index of the ULBWP are the same. And, based on the detection of the downlink signal(e.g., the PDCCH 501 a-d) on the DL BWP(s) (e.g., on the active DLBWP(s)), the UE 102 performs the UL transmission corresponding to theconfigured grant on the UL BWP(s) (e.g., on the active UL BWP(s)) linkedwith the DL BWP(s) on which the downlink signal is detected.

For example, the UL transmission(s) may be dynamically scheduled by anuplink grant in a DCI (e.g., the DCI format(s) for the uplink with theCRC scrambled by the C-RNTI). Additionally or alternatively, the ULtransmission(s) may correspond to a configured grant Type 1 and/or aconfigured grant Type 2. The transmission corresponds to the configuredgrant Type 1 may be semi-statically configured to operate upon thereception of a parameter(s) of ConfiguredGrantConfig includingrrc-ConfiguredUplinkGrant without the detection of an uplink grant in aDCI (e.g., the DCI format(s) for the uplink). The transmissioncorresponds to the configured grant Type 2 may be scheduled by an uplinkgrant in a valid activation DCI (e.g., the activation DCI format(s) forthe uplink with the CRC scrambled by the CS-RNTI) after the reception ofthe parameter(s) of the ConfiguredGrantConfig not includingrrc-ConfiguredUplinkGrant.

Namely, the UL transmission(s) corresponding to the configured grant(s)may be scheduled (e.g., activated) by using the DCI format(s) with theCRC scrambled by the CS-RNTI. And, two types of the UL transmission(s)correspond to the configured grant(s). For example, one of the two typesof the UL transmission(s) may be referred to as a transmissioncorresponding to a configured grant Type 1 (e.g., a configured grantType 1 transmission, UL transmission for the configured grant Type 1).Also, one of the two types of the UL transmission(s) may be referred toas a transmission corresponding to a configured grant Type 2 (e.g., aconfigured grant Type 2 transmission, UL transmission for the configuredgrant Type 2).

Here, for the configured grant Type 1 transmission, an uplink grant maybe provided by the RRC (e.g., the RRC layer). For example, in a casethat the UE 102 receives the RRC message including the uplink grant(e.g., the configuration(s) for the configured grant Type 1transmission), the UE 102 may store the uplink grant as a configuredgrant.

Also, for the configured grant Type 2, an uplink grant may be providedby the PDCCH 501 (e.g., the activation DCI format(s) to be used forindicating the activation, a configured grant activation, and/or anactivation of a configured grant (e.g., a configured grant correspondingto a configured grant configuration)). For example, in a case that theUE 102 receives the uplink grant (e.g., the activation DCI format(s)),the UE 102 may store the uplink grant as the configured grant. Also, ina case that the UE 102 receives the uplink grant (e.g., a deactivationDCI format(s) to be used for indicating the deactivation, a configuredgrant deactivation, and/or a deactivation of a configured grant (e.g., aconfigured grant corresponding to a configured grant configuration)),the UE 102 clear the configured uplink grant (e.g., a configuredgrant(s) corresponding to a deactivated configured grant configurationwith an index). Namely, the uplink grant provided by the PDCCH 501 maybe stored as the configured grant based on the DCI format (e.g., L1signaling) indicating the configured grant activation (e.g., the DCIformat(s) used for indicating an activation of a configured grant).Additionally or alternatively, the uplink grant provided by the PDCCH501 may be cleared based on the DCI format (e.g., L1 signaling)indicating the configured grant deactivation (e.g., the DCI format(s)used for indicating a deactivation of a configured grant).

Namely, for the configured grant type 2 transmission, the DCI format(s)with CRC scrambled by the CS-RNTI may be used for indicating theactivation (e.g., the configured grant activation). Also, for theconfigured grant Type 2 transmission, the DCI format(s) with CRCscrambled by the CS-RNTI may be used for indicating a deactivation(e.g., the configured grant deactivation).

Here, the DCI format(s) with CRC scrambled by the CS-RNTI may be usedfor indicating a retransmission(s) (e.g., the retransmission(s) of theTB(s) (e.g., the retransmission of the TB(s) transmitted by theconfigured grant Type 1 transmission, and/or the configured grant Type 2transmission)). For example, the retransmission(s) may be indicated byusing the NDI set to “1” (i.e., the NDI field set to “1”, the NDI=“1”).Here, as described above, the NDI (i.e., the NDI field) may be includedin the DCI format(s) with CRC scrambled by the CS-RNTI. Namely, thePUSCH retransmission may be scheduled by using the PDCCH 501 (e.g., theDCI format(s) for the uplink) with the CRC scrambled by the CS-RNTI withNDI set to “1”.

Here, for example, for the configured grant Type 1 transmission, basedon configuration(s) of the configured grant Type 1 (e.g., for theserving cell(s)), the UE 102 may store the uplink grant as theconfigured grant (e.g., for the serving cell(s)). Also, the UE 102 mayinitialize (if not active) or re-initialize (if already active) theconfigured grant to start in the symbol according to the parameter(s)(e.g., timeDomainoffset) and reoccur with the parameter (e.g.,periodicity). And, after the uplink grant is configured for theconfigured grant Type 1, the UE 102 may consider sequentially that theNth uplink grant occurs associated with the symbol for which:

[(SFN*numberOfSlotsPerFrame*numberOjSymbolsPerSlot)+(slot number in theframe*numberOfSymbolsPerSlot)+symbol number in theslot]=(timeDomainOffset+N*periodicity)modulo 1024.  (1)

Also, for example, for the configured grant Type 2 transmission, afterthe uplink grant is configured for the configured grant Type 2, the UE102 may consider sequentially that the Nth uplink grant occursassociated with the symbol for which:

[(SFN*numberOfSlotsPerFrame*numberOfSymbolsPerSlot)+(slot number in theframe*numberOfSymbolsPerSlot)+symbol number in theslot]=[(SFN_(start time)*numberOfSlotsPerFrame*numberOfSymbolsPerSlot+slot_(start time)*numberOfSymbolsPerSlot+symbol_(start time))+N*periodicity]modulo1024.  (2)

Here, SFN_(start time), slot_(start time), and symbol_(start time) arethe SFN (i.e., System Frame Number), slot, and symbol, respectively, atthe time the configured uplink grant was (re-)initialised. Also, forexample, the parameter (e.g., periodicity) may be configured by the gNB160 by using the RRC message.

Namely, for the configured grant Type 1 transmission, the UE 102 mayinitiate the uplink transmission based on the reception of theparameter(s) included in the RRC message. Also, for the configured granttype 2 transmission, the UE 102 may initiate the uplink transmissionbased on the reception of the DCI format(s) for the uplink with the CRCscrambled by the C-RNTI. Also, the UE 102 may perform the retransmissionof the TB(s) (e.g., the retransmission on the UL-SCH, the retransmissionon the PUSCH 503) based on the reception of the DCI format(s) for theuplink with the CRC scrambled by the C-RNTI, where the NDI included inthe DCI format(s) for the uplink is set to “1”.

For example, the gNB 160 may transmit, by using the RRC message (e.g.,the dedicated RRC message, a UE-specific RRC message), the parameter(s)used for the configured grant Type 1 transmission. And, the UE 102 mayperform the configured grant Type 1 transmission based on theparameter(s) included in the RRC message. Also, the gNB 160 maytransmit, by using the RRC message (e.g., the dedicated RRC message, theUE-specific RRC message), the parameter(s) for the configured grant Type2 transmission. And, the UE 102 may perform the configured grant Type 2transmission based on the parameter(s) included in the RRC message.

Here, for the transmission(s) corresponding to the configured grant(s)(i.e., the configured grant Type 1 transmission and/or the configuredgrant Type 2 transmission), the following parameters may be configured.For example, the following parameters may be includedConfiguredGrantConfig in the ConfiguredGrantConfig information element(IE). Namely, the RRC message may include the ConfiguredGrantConfig IE.

-   -   frequencyhopping: the value “intraSlot” enables “Intra-slot        frequency hopping and the value “interSlot” enables “Inter-slot        frequency hopping”    -   mcs-Table: indicates a MCS table the UE 102 shall use for the        PUSCH (e.g., the PUSCH transmission) (e.g., without transform        precoding)    -   mcs-TableTransformPrecoder: indicates a MCS table the UE 102        shall use for the PUSCH (e.g., the PUSCH transmission) (e.g.,        with transform precoding)    -   powerControlLoopToUse: closed control loop to apply. A        parameter(s) used to determine a transmission power for the        PUSCH transmission (e.g., the transmission(s) corresponding to        the configured grant(s))    -   p0-PUSCH-Alpha: an index of P0-PUSCH-AlphaSet to be used for        this configuration. A parameter(s) used to determine the        transmission power for the PUSCH transmission (e.g., the        transmission(s) corresponding to the configured grant(s))    -   transfbrmPrecoder: enables or disables transform precoding for        the transmission(s) corresponding to the configured grant(s)        (i.e., the configured grant Type1 transmission and/or the        configured grant Type2 transmission)    -   nrofHARQ-Processes: the number of HARQ processes configured for        the configured grant Type 1 transmission and/or the configured        grant Type 2 transmission    -   repK: the number of repetitions to be applied for the configured        grant Type 1 transmission and/or the configured grant Type 2        transmission    -   repK-RV: the redundancy version sequence to be applied for the        configured grant Type 1 transmission and/or the configured grant        Type 2 transmission

Additionally or alternatively, for the configured grant Type 1transmission, the following parameter(s) may be configured. For example,the flowing parameters may be included in rrc-ConfiguredUplinkGrant inthe ConfiguredGrantConfig IE.

-   -   timeDomainOffset: an offset value(s) related to System Frame        Number (SFN)=0. Namely, an offset value(s) used for indicating a        timing(s) for the configured grant Type 1 transmission.    -   timeDomainAllocation: indicates a combination of start symbol        and length and PUSCH mapping type    -   frequencyDomainAllocation: indicates the frequency domain        resource allocation    -   antenna port: indicates the antenna port(s) to be used for this        configuration    -   mcsAndTBS: indicates the modulation order, target code rate        and/or TB size    -   frequencyHoppingOffset: frequency hopping offset used when        frequency hopping is enabled    -   pathlossReferenceIndex: a parameter(s) for a power control for        the configured grant Type 1 transmission (i.e., to be used for        this configuration)

Here, multiple configurations of ConfiguredGrantConfig may be supported.Namely, one or more configurations of ConfiguredGrantConfig may beconfigured. Also, multiple configurations of rrc-ConfiguredUplinkGrantmay be supported. Namely, one or more configurations ofac-ConfiguredUplinkGrant may be configured. Here, the configuration(s)of ConfiguredGrantConfig and/or the configuration(s) ofrrc-ConfiguredUplinkGrant may be referred to as the configuration(s) ofthe configured grant. Namely, a single configuration of the configuredgrant may be supported. Also, multiple configurations of the configuredgrant may be supported.

For example, the gNB 160 may transmit, by using the RRC message, thirdinformation used for configuring that the multiple configurations of theconfigured grant are enabled (e.g., allowed). Namely, the gNB 160 maytransmit, by using the RRC message, the third information used forindicating whether the single configuration of the configured grant orthe multiple configurations of the configured grant is used for thetransmission(s) that corresponds to the configured grant(s).

Namely, in a case that the single configuration of the configured grantis configured, the single configuration of the configured grant may beused for the transmission(s) corresponding to the configured grant(s).Also, in a case that the multiple configurations of the configured grantare configured, the multiple configurations of the configured grant maybe used for the transmission(s) corresponding to the configuredgrant(s). Also, in a case that the multiple configurations of theconfigured grant are not configured, the single configuration of theconfigured grant may be used for the transmission(s) corresponding tothe configured grant(s).

Here, the third information may be configured per serving cell. Forexample, the third information may be configured for each of servingcells (e.g., the primary cell and/or the one or more secondary cells).Additionally or alternatively, the third information may be configuredper UL bandwidth part (UL BWP). For example, the third information maybe configured for each of UL BWPs (e.g., each of UL BWPs in the servingcell). Additionally or alternatively, the third information may beconfigured for the configured grant Type 1 transmission and/or theconfigured grant Type 2 transmission. For example, the third informationmay be commonly configured for the configured grant Type 1 transmissionand the configured grant Type 2 transmission. Additionally oralternatively, the third information may be separately configured forthe configured grant Type 1 transmission and the configured grant Type 2transmission.

For example, as described below, in a case that the third information iscommonly configured for the configured grant Type 1 transmission and theconfigured grant Type 2 transmission, an index of the configuration(s)may be configured for the ConfiguredGrantConfig. Additionally oralternatively, in a case that the third information is separatelyconfigured for the configured grant Type 1 transmission and theconfigured grant Type 2 transmission, an index of the configuration(s)index may be configured for the ConfiguredGrantConfig and/or an index ofthe configuration(s) may be configured for therrc-ConfiguredUplinkGrant.

Additionally or alternatively, the single configuration of theconfigured grant may be activated. Namely, the single activeconfiguration of the configured grant may be supported. Additionally oralternatively, the multiple configurations of the configured grant maybe activated. Namely, the multiple active configurations of theconfigured grant may be supported. For example, the multiple activeconfigurations of the configured grant for a given BWP (e.g., an UL BWP)of the serving cell may be supported at lease for differentservices/traffic type and/or for enhancing reliability and reducinglatency.

Namely, the single configuration of the configured grant may beconfigured (and/or activated) for a given BWP (e.g., an UL BWP) of asingle serving cell. Additionally or alternatively, the multipleconfigurations of the configured grant may be configured (and/oractivated) for a given BWP (e.g., an UL BWP) of a single serving cell.

The UE 102 may perform the configured grant Type 1 transmission based onthe single configuration of the configured grant (if the singleconfiguration of the configured grant is used) and/or the multipleconfigurations of the configured grant (if the multiple configurationsof the configured grant are used).

Additionally or alternatively, for the transmission on the PUSCH 503,the following parameter(s) may be configured. For example, the flowingparameters may be included in PUSCH-Config in PUSCH-Config IE (e.g.,included in BWP-Uplink Dedicated IE). The IE PUSCH-Config may be usedfor configuring UE-specific parameters applicable to a particular BWP(e.g., the UL BWP). Also, the IE BWP-Uplink Dedicated may be used forconfiguring the dedicated parameters (i.e., UE specific parameters) ofthe UL BWP. Namely, the gNB 160 may transmit, by using the RRC message(e.g., the dedicated RRC message, the UE-specific RRC message), theparameter(s) used for the transmission on the PUSCH 503. For example,the following parameter(s) may be used for the transmission on the PUSCH503 scheduled by using the DCI format(s) with the CRC scrambled by theC-RNTI.

-   -   dataScramblingldentityPUSCH: identifier used to initiate data        scrambling for the PUSCH (e.g., the PUSCH transmission)    -   txConfig: indicates whether the UE uses codebook based        transmission or non-codebook based transmission    -   PUSCH-PowerControl: the parameter(s) used to determine the        transmission power for the PUSCH transmission    -   frequencyHopping: the value “intraSlot” enables “Intra-slot        frequency hopping and the value “interSlot” enables “Inter-slot        frequency hopping”    -   pusch-TimeDomainAllocationList: list of time domain resource        assignment for timing of the DCI format(s) for the uplink and        the UL transmission    -   pusch-AggregationFactor: the number of repetitions for the UL        transmission(s) (e.g., the PUSCH transmission(s))    -   mcs-Table: indicates which MCS table the UE shall use for the        PUSCH transmission (e.g., without transform precoding)    -   mcs-TableTransformPrecoder: indicates which MCS table the UE        shall use for the PUSCH transmission (e.g., with transform        precoding)    -   transformPrecoder: UE-specific selection of transformer precoder        for the PUSCH transmission    -   scaling of UCI-OnPUSCH: indicates a scaling factor to limit the        number of resource elements assigned to UCI transmitted on the        PUSCH

Here, the parameter PUSCH-PowerControl may include the followingparameters.

-   -   tpc-Accumulation: if enabled, the UE 102 applies transmission        power (TPC) command via accumulation. If not enabled, the UE 102        applies the TPC command without accumulation. A parameter        indicates a configuration for the TPC command (e.g., whether the        TPC command is accumulated or nor accumulated (i.e., an absolute        value is used as the TPC command))    -   p0-NominalWithoutGrant: the parameter(s) used to determine the        transmission power for the transmission(s) corresponding to the        configured grant(s)    -   p0-Alpha: the parameter(s) used to determine the transmission        power for the PUSCH transmission

Here, multiple configurations of PUSCH-Config may be supported. Namely,one or more configurations of PUSCH-Config may be configured. Here, theconfiguration(s) of PUSCH-Config may be referred to as theconfiguration(s) of the PUSCH 503. Namely, a single configuration of thePUSCH 503 may be supported. Also, multiple configurations of the PUSCH503 may be supported.

For example, the multiple configurations of the PUSCH 503 may beconfigured in a case that the multiple configurations of the configuredgrant are configured. Namely, in a case that the gNB 160 configure themultiple configuration of the configured grant, the gNB 160 may alwaysconfigure the multiple configurations of the PUSCH 503. For example, thesingle configuration of the PUSCH 503 may be configured in a case thatthe single configuration of the configured grant is configured. Namely,in a case that the gNB 160 configure the single configuration of theconfigured grant, the gNB 160 may always configure the singleconfiguration of the PUSCH 503.

Here, in a case that the multiple configurations of the configured grantare configured, the index of the configuration(s) may be configured. Forexample, the index of the configuration may be included in theConfiguredGrantConfig (e.g., or the ConfiguredGrantConfig IE).Additionally or alternatively, the index of the configuration(s) may beincluded in the ac-ConfiguredUplinkGrant (e.g., in theConfiguredGrantConfig IE). Additionally or alternatively, the index ofthe configuration(s) may be included in the PUSCH-config.

Here, the index of the configuration may be the index of theconfiguration for the ConfiguredGrantConfig. Additionally oralternatively, the index of the configuration may be the index of theconfiguration for the ac-ConfiguredUplinkGrant. Additionally oralternatively, the index of the configuration may be the index of theconfiguration for the PUSCH-Config.

Namely, each of the multiple configurations of the configured grant maybe identified by using the index of the configuration(s) (e.g., theindex of the configured grant configuration(s)). Also, each of themultiple configurations of the PUSCH 503 may be identified by using theindex of the configuration(s) (e.g., the index of the PUSCHconfiguration(s)). Also, a linkage between each of the multipleconfigurations of the configured grant and each of the multipleconfigurations of the PUSCH 503 (e.g., a correspondence for the each ofthe multiple configurations of the configured grant and the each of themultiple configurations of the PUSCH 503) may be identified by using theindex of the configuration(s).

For example, in a case that the multiple configurations of theconfigured grant (e.g., four configurations of the configured grant) areconfigured for the configured grant transmission, the index “0” (e.g.,the value “0”), the index “1” (e.g., the value “1”), the index “2”(e.g., the value “2”) and/or the index “3” (e.g., the value “3”) may beconfigured as the index of the configuration(s) for the each of themultiple configurations of the configured grant.

For example, the index “0” may be configured for a first configurationof the multiple configurations of the configured grant (e.g., as theconfiguration index #0). Also, the index “1” may be configured for asecond configuration of the multiple configurations of the configuredgrant (e.g., as the configuration index #1). Also, the index “2” may beconfigured for a third configuration of the multiple configurations ofthe configured grant (e.g., as the configuration index #2). Also, theindex “1” may be configured for a fourth configuration of the multipleconfigurations of the configured grant (e.g., as the configuration index#3).

For example, in a case that the multiple configurations of the PUSCH(e.g., four configurations of the PUSCH) are configured, the index “0”,the index “1”, the index “2” and/or the index “3” may be configured asthe index of the configuration(s) for the each of the multipleconfigurations of the PUSCH 503. Namely, in a case the multipleconfigurations of the PUSCH 503 (e.g., four configurations of the PUSCH503) are configured, the index “0”, the index “1”, the index “2” and/orthe index “3” may be configured as the index of the configuration(s) forthe each of the multiple configurations of the PUSCH 503.

For example, the index “0” may be configured for a first configurationof the multiple configurations of the PUSCH (e.g., as the configurationindex #0). Also, the index “1” may be configured for a secondconfiguration of the multiple configurations of the PUSCH (e.g., as theconfiguration index #1). Also, the index “2” may be configured for athird configuration of the multiple configurations of the PUSCH (e.g.,as the configuration index #2). Also, the index “1” may be configuredfor a fourth configuration of the multiple configurations of the PUSCH(e.g., as the configuration index #3).

And, in a case that the index of the configuration of the configuredgrant and the index of the configuration of the PUSCH 503 is the same,the configuration of the configured grant may be linked with theconfiguration of the PUSCH 503. Namely, the configuration of theconfigured grant and the configuration of the PUSCH 503 may be linked ina case that the index of the configuration of the configured grant andthe index of the configuration of the PUSCH 503 is the same.

Here, one of the multiple configurations of the configured grant (e.g.,the configuration of the configured grant with the index “X (X=0, 1, 2,or 3)” (e.g., an index corresponding to the one of the multipleconfigurations of the configured grant)) may be defined, in advance, bythe specification, and may be known information between the gNB 160 andthe UE 102. Additionally or alternatively, the one of the multipleconfigurations of the configured grant may be configured by the gNB 160.For example, the gNB 160 may transmit, by using the RRC message,information used for configuring the one of the multiple configurationsof the configured grant (e.g., the index corresponding to the one or themultiple configurations of the configured grant). The UE 102 mayidentify the one of the multiple configurations of the configured grant(e.g., the index corresponding to the one of the multiple configurationsof the configured grant) based on the information. Here, the one of themultiple configurations of the configured grant may be referred to as aconfiguration with the index “X”. Namely, the index corresponding to theone of the multiple configurations of the configured grant may bereferred to as the index “X”.

As described above, the configuration with the index “X” may be theconfiguration with the index “0”. Additionally or alternatively, theconfiguration with the index “X” may be the configuration with the index“1”. Additionally or alternatively, the configuration with the index “X”may be the configuration with the index “2”. Additionally oralternatively, the configuration with the index “X” may be theconfiguration with the index “3”. Namely, the configuration with theindex “X” may be the configuration with the index of “a predeterminedvalue”.

Additionally or alternatively, the index of the configuration of theconfigured grant may not be configured for (e.g., applied for) theconfiguration with the index “X”. For example, the index of theconfiguration of the configured grant may be configured only for (e.g.,applied only for) the configuration of the configured grant other thanthe configuration with the index “X”.

Additionally or alternatively, in a case that the single configurationof the configured grant is used, the single configuration of theconfigured grant may correspond to the configuration with the index “X”.Additionally or alternatively, in a case that the single configurationof the configured grant is used, the single configuration of the PUSCH503 may be linked with the configuration with the index “X”.Additionally or alternatively, in a case that the single configurationof the PUSCH 503 is used, the single configuration of the PUSCH 503 maybe linked with the configuration with the index “X”

Here, the configuration of the configured grant other than theconfiguration with the index “X” may include a part of the parametersincluded in the PUSCH-config. And, the configuration with the index “X”may not include a part of the parameters included in the PUSCH-config.

Namely, the configuration of the configured grant other than theconfiguration with the index “X” may includedataScramblingIdentityPUSCH, txConfig, PUSCH-PowerControl,frequencyHopping, pusch-TimeDomainAllocationList,pusch-AggregationFactor, mcs-Table, mcs-TableTransformPrecoder, and/orscaling of UCI-OnPUSCH.

For example, the configuration of the configured grant other than theconfiguration with the index “X” may includedataScramblingIdentityPUSCH, txConfig, and/or scaling of UCI-OnPUSCH.And, the configuration of the configured grant other than theconfiguration with the index “X” may not include PUSCH-PowerControl,frequencyHopping, pusch-TimeDomainAllocationList,pusch-AggregationFactor, mcs-Table, and/or mcs-TableTransformPrecoder.

Namely, in a case that the multiple configurations of the configuredgrant are configured, a part of the parameters (e.g., described as theparameter(s) included in the PUSCH-config) may be configured in theConfiguredGrantConfig IE (e.g., the ConfiguredGrantConfig and/or theac-ConfiguredUplinkGrant).

Additionally or alternatively, the configuration of the PUSCH 503 linkedwith the configuration of the configured grant other than theconfiguration with the index “X” may include a part of the parameter(s)(e.g., a part of the parameters included in the PUSCH-config). And, theconfiguration of the PUSCH 503 linked with the configuration with theindex “X” may include the parameter(s) (e.g., the all parametersincluded in the PUSCH-config described above).

Namely, the configuration of the PUSCH 503 linked with the configurationof the configured grant other than the configuration with the index “X”may not include dataScramblingIdentityPUSCH, txConfig,PUSCH-PowerControl, frequencyHopping, pusch-TimeDomainAllocationList,pusch-AggregationFactor, mcs-Table, mcs-TableTransformPrecoder, and/orscaling of UCI-OnPUSCH.

For example, the configuration of the PUSCH 503 linked with theconfiguration of the configured grant other than the configuration withthe index “X” may include dataScramblingIdentityPUSCH, txConfigtpc-Accumulation, and/or scaling of UCI-OnPUSCH. And, the configurationof the PUSCH 503 linked with the configuration of the configured grantother than the configuration with the index “X” may not includep0-NominalWithoutGrant, p0-Alpha, frequencyHopping,pusch-TimeDomainAllocationList, pusch-AggregationFactor, mcs-Table,and/or mcs-TableTransformPrecoder.

Namely, only a part of the parameters (e.g., the parameters included inthe PUSCH-config) may be configured to the multiple configurations(e.g., the multiple configurations of the PUSCH 503). Namely, based onthat the multiple configurations of the configured grant are configured,a part of the parameters (e.g., a part of the parameters included in thePUSCH-config) may be configured to the multiple configurations.

Here, in a case that the single configuration of the configured grant isconfigured (i.e., in a case that the multiple configurations of theconfigured grant are not configured), the UE 102 may perform thetransmission(s) corresponding to the configured grant(s) based on thesingle configuration of the configured grant(s).

For example, for the configured grant Type 1 transmission, in a casethat the configuration of the configured grant with the index “1” isconfigured, the UE 102 may perform the transmission corresponding to theconfigured grant based on the configuration of the configured grant withthe index “1” (i.e., the parameter(s) included in the configuration ofthe configured grant with the index “1”). Additionally or alternatively,as described above, for the configured grant Type 1 transmission, in acase that the single configuration of the configured grant isconfigured, the UE 102 may perform the transmission corresponding to theconfigured grant based on the configuration with the index “X”. Namely,in a case that the single configuration of the configured grant isconfigured, the configuration with the index “X” may be always appliedfor the transmission corresponding to the configured grant.

Additionally or alternatively, for the configured grant Type 2transmission, in a case that the single configuration of the configuredgrant is configured, the UE 102 may identify the index of theconfiguration of the configured grant (i.e., the index of theconfiguration of the configured grant to be applied for thetransmission) based on the information included in the DCI format(s)with the CRC scrambled by the CS-RNTI (e.g., the DCI format(s) used forindicating the activation of the configured grant). Namely, the DCIformat(s) may include the information used for indicating the index ofthe configuration of the configured grant.

For example, for the configured grant Type 2 transmission, in a casethat the single configuration of the configured grant is configured andthe configuration of the configured grant with the index “1” isindicated by using the DCI format(s) with the CRC scrambled by theCS-RNTI, the UE 102 may perform the transmission corresponding to theconfigured grant based on the configuration of the configured grant withthe index “1” (i.e., the parameter(s) included in the configuration ofthe configured grant with the index “1”). Namely, the configuration ofthe configured grant with the index “1” may be activated by using theDCI format(s) with the CRC scrambled by the CS-RNTI. Additionally oralternatively, as described above, for the configured grant Type 2transmission, in a case that the single configuration of the configuredgrant is configured, the UE 102 may perform the transmissioncorresponding to the configured grant based on the configuration withthe index “X”. Namely, in a case that the single configuration of theconfigured grant is configured, the configuration with the index “X” maybe always applied for the transmission corresponding to the configuredgrant.

Additionally or alternatively, for the retransmission(s) scheduled byusing the DCI format(s) with the CRC scrambled by the CS-RNTI with theNDI set to “1”, in a case that the single configuration of theconfigured grant is configured, the UE 102 may identify the index of theconfiguration of the PUSCH 503 (i.e., the index of the configuration ofthe PUSCH 503 to be applied for the transmission) based on theinformation included in the DCI format(s) with the CRC scrambled by theCS-RNTI with the NDI set to “1”. Namely, the DCI format(s) for theuplink may include the information used for indicating the index of theconfiguration of the PUSCH 503.

For example, in a case that the single configuration of the configuredgrant is configured and the configuration of the PUSCH 503 with theindex “1” is indicated by using the DCI format(s) with the CRC scrambledby the CS-RNTI with the NDI set to “1”, the UE 102 may perform theretransmission(s) based on the configuration of the PUSCH 503 with theindex “1” (i.e., the parameter(s) included in the configuration of thePUSCH 503 with the index “1”). Namely, the configuration of the PUSCH503 with the index “1” may be activated by using the DCI format(s) withthe CRC scrambled by the CS-RNTI with the NDI set to “1”. Additionallyor alternatively, as described above, in a case that the singleconfiguration of the configured grant is configured, the UE 102 mayperform the retransmission(s) based on the configuration of the PUSCH503 linked with the configuration with the index “X”. Namely, in a casethat the single configuration of the configured grant is configured, theconfiguration of the PUSCH 503 linked with the configuration with theindex “X” may be always applied for the retransmission(s).

Additionally or alternatively, only in a case that the multipleconfigurations of the configured grant are configured, the informationused for indicating the index of the configuration of the configuredgrant may be included in the DCI format(s). Namely, in a case that thesingle configuration of the configured grant is configured, theinformation used for indicating the index of the configuration of theconfigured grant may not be included in the DCI format(s) for the uplinkgrant. Here, as described below, the information used for indicating theindex of the configuration of the configured grant may be included inonly the DCI format 0_1.

Additionally or alternatively, only in a case that the multipleconfigurations of the configured grant are configured, the informationused for indicating the index of the configuration of the PUSCH 503 maybe included in the DCI format(s). Namely, in a case that the singleconfiguration of the configured grant is configured, the informationused for indicating the index of the configuration of the PUSCH 503 maynot be included in the DCI format(s). Here, as described below, theinformation used for indicating the index of the configuration of thePUSCH 503 may be included in only the DCI format 0_1.

Additionally or alternatively, in a case that the multipleconfigurations of the configured grant are configured, the UE 102 mayperform the transmission(s) corresponding to the configured grant(s)based on the multiple configurations of the configured grant(s).

For example, for the configured grant Type 1 transmission, in a casethat the configuration with the index “1” and the configurations withthe index with “3” are configured, the UE 102 may perform thetransmission corresponding to the configured grant based on theconfiguration of the configured grant with the index “1” and theconfiguration of the configured grant with index “3” (i.e., theparameter(s) included in the configuration of the configured grant withthe index “1” and the parameter(s) included in the configuration of theconfigured grant with the index “3”).

Additionally or alternatively, for the configured grant Type 2transmission, in a case that the multiple configurations of theconfigured grant are configured, the UE 102 may identify the index ofthe configuration(s) of the configured grant(s) (i.e., the index of theconfiguration(s) of the configured grant(s) to be applied for thetransmission) based on the information included in the DCI format(s)with the CRC scrambled by the CS-RNTI (e.g., the DCI format(s) used forindicating the activation of the configured grant).

For example, for the configured grant Type 2 transmission, in a casethat the multiple configurations of the configured grant are configuredand the configuration of the configured grant with the index “1” isindicated by using the DCI format(s) with the CRC scrambled by theCS-RNTI, the UE 102 may perform the transmission corresponding to theconfigured grant based on the configuration with the index “1” (i.e.,the parameter(s) included in the configuration of the configured grantwith the index “1”). Namely, the configuration of the configured withthe index “1” may be activated by using the DCI format(s) with the CRCscrambled by the CS-RNTI. Also, in a case that the multipleconfigurations of the configured grant are configured and theconfiguration of the configured grant with the index “3” is indicated bythe DCI format(s) with the CRC scrambled by the CS-RNTI, the UE 102 mayperform the transmission corresponding to the configured grant based onthe configuration with the index “3” (i.e., the parameter(s) included inthe configuration of the configured grant with the index “3”). Namely,the configuration of the configured grant with the index “3” may beactivated by using the DCI format(s) with the CRC scrambled by theCS-RNTI.

Here, the multiple configurations of the configured grant may beactivated simultaneously (e.g., at the same time) by using the singleDCI format with the CRC scrambled by the CS-RNTI. Namely, the single DCIformat may include the information used for indicating one or moreindices of the configuration(s) of the configured grant to be appliedfor the transmission corresponding to the configured grant. For example,in a case that the multiple configurations are configured, and theconfiguration of the configured grant with the index “1” and theconfiguration of the configured grant with the index “3” are indicated,the UE 102 may perform the transmission corresponding to the configuredgrant based on the configuration of the configured grant with the index“1” and the configuration of the configured grant with the index “3”.

Additionally or alternatively, for the retransmission(s) scheduled byusing the DCI format(s) with the CRC scrambled by the CS-RNTI with theNDI set to “1”, in a case that the multiple configurations of theconfigured grant are configured, the UE 102 may identify the index ofthe configuration of the PUSCH 503 (i.e., the index of the configurationof the PUSCH 503 to be applied for the transmission) based on theinformation included in the DCI format(s) with the CRC scrambled by theCS-RNTI with the NDI set to “1”. Namely, the DCI format(s) for theuplink may include the information used for indicating the index of theconfiguration of the PUSCH 503.

For example, in a case that the multiple configurations of theconfigured grant are configured and the configuration of the PUSCH 503with the index “1” is indicated by using the DCI format(s) with the CRCscrambled by the CS-RNTI with the NDI set to “1”, the UE 102 may performthe retransmission(s) based on the configuration of the PUSCH 503 withthe index “1” (i.e., the parameter(s) included in the configuration ofthe PUSCH 503 with the index “1”). Namely, the configuration of thePUSCH 503 with the index “1” may be activated by using the DCI format(s)with the CRC scrambled by the CS-RNTI with the NDI set to “1”. Also, ina case that the multiple configurations of the configured grant areconfigured and the configuration of the PUSCH 503 with the index “3” isindicated by using the DCI format(s) with the CRC scrambled by theCS-RNTI with the NDI set to “1”, the UE 102 may perform theretransmission(s) based on the configuration of the PUSCH 503 with theindex “3” (i.e., the parameter(s) included in the configuration of thePUSCH 503 with the index “3”). Namely, the configuration of the PUSCH503 with the index “3” may be activated by using the DCI format(s) withthe CRC scrambled by the CS-RNTI with the NDI set to “1”.

Here, the multiple configurations of the PUSCH 503 may be activatedsimultaneously (e.g., at the same time) by using the single DCI formatwith the CRC scrambled by the CS-RNTI with the NDI set to “1”. Namely,the single DCI format may include the information used for indicatingone or more indices of the configuration(s) of the PUSCH 503 to beapplied for the retransmission(s). For example, in a case that themultiple configurations are configured, and the configuration of thePUSCH 503 with the index “1” and the configuration of the PUSCH 503 withthe index “3” are indicated, the UE 102 may perform theretransmission(s) based on the configuration of the PUSCH 503 with theindex “1” and the configuration of the PUSCH 503 with the index “3”.

Additionally or alternatively, for the transmission(s) corresponding tothe configured grant(s) (i.e., the configured grant Type 1 and/or theconfigured grant Type 2), the UE 102 may apply the parameter(s) providedby the ConfiguredGrantConfig expect for dataScramblingIdentityPUSCH,txConfig, and/or scaling of UCI-OnPUSCH, which are provided by thePUSCH-config. Namely, for the transmission(s) corresponding to theconfigured grant(s), the UE 102 may apply a part of the parameter(s)included in the ConfiguredGrantConfig. Also, for the transmission(s)corresponding to the configured(s), the UE 102 may apply a part of theparameter(s) (e.g., dataScramblingldentityPUSCH, txConfig, and/orscaling of UCI-OnPUSCH) included in the PUSCH-config.

Additionally or alternatively, for the retransmission(s) scheduled byusing the DCI format(s) with the CRC scrambled by the CS-RNTI with theNDI set to “1”, the UE 102 may apply the parameter(s) provided thePUSCH-config expect for p0-NominalWithoutGrant, p0-PUSCH-Alpha,mcs-Table, mcs-TableTransformPrecoder, and/or transformPrecoder.

For example, for the retransmission(s) scheduled by using the DCIformat(s) with the CRC scrambled by the CS-RNTI with the NDI set to “1”,the UE 102 may apply the parameter(s) provides the PUSCH-config expectfor p0-NominalWithoutGrant, p0-PUSCH-Alpha, mcs-Table,mcs-TableTransformPrecoder, and/or transformPrecoder. And, instead ofp0-NominalWithoutGrant, p0-PUSCH-Alpha, mcs-Table,mcs-TableTransformPrecoder, and/or transformPrecoder included in thePUSCH-config, p0-PUSCH-Alpha, mcs-Table, mcs-TableTransformPrecoder,and/or transformPrecoder included in the ConfiguredGrantConfig may beapplied for the retransmission(s). Namely, for the retransmission(s)scheduled by using the DCI format(s) with the CRC scrambled by theCS-RNTI with the NDI set to “1”, the UE 102 may apply a part of theparameter(s) (e.g., p0-PUSCH-Alpha, mcs-Table,mcs-TableTransformPrecoder, and/or transformPrecoder) included in theConfiguredGrantConfig. Also, for the retransmission(s) scheduled byusing the DCI format(s) with the CRC scrambled by the CS-RNTI with theNDI set to “1”, the UE 102 may apply a part of the parameter(s) includedin the PUSCH-config.

Here, in a case that the UE 102 applies a part of parameter(s) includedin the ConfiguredGrantConfig and a part of parameter(s) included in thePUSCH-config, the configuration of the configured grant and theconfiguration of the PUSCH 503 that are linked may be used for the(re)transmission.

Namely, for the (re)transmission(s), in a case that the configuration ofthe configured grant with the index “0” is applied (i.e., in a case thata part of the parameter(s) of the configuration of the configured grantwith the index “0” is applied), the configuration of the PUSCH 503 withthe index “0” (i.e., a part of the parameter(s) of the configuration ofthe PUSCH 503 with the index “0”) may be applied. Also, for the(re)transmission(s), in a case that the configuration of the configuredgrant with the index “1” is applied (i.e., in a case that a part of theparameter(s) of the configuration of the configured grant with the index“1” is applied), the configuration of the PUSCH 503 with the index “1”(i.e., a part of the parameter(s) of the configuration of the PUSCH 503with the index “1”) may be applied. Also, for the (re)transmission(s),in a case that the configuration of the configured grant with the index“2” is applied (i.e., in a case that a part of the parameter(s) of theconfiguration of the configured grant with the index “2” is applied),the configuration of the PUSCH 503 with the index “2” (i.e., a part ofthe parameter(s) of the configuration of the PUSCH 503 with the index“2”) may be applied. Also, for the (re)transmission(s), in a case thatthe configuration of the configured grant with the index “3” is applied(i.e., in a case that a part of the parameter(s) of the configuration ofthe configured grant with the index “3” is applied), the configurationof the PUSCH 503 with the index “3” (i.e., a part of the parameter(s) ofthe configuration of the PUSCH 503 with the index “3”) may be applied.

Also, for the (re)transmission(s), in a case that the configuration ofthe configured grant with the index “X” is applied (i.e., in a case thata part of the parameter(s) of the configuration of the configured grantwith the index “X” is applied), the configuration of the PUSCH 503linked with the configured with the index “X” (i.e., a part of theparameter(s) of the configuration of the PUSCH 503 linked with theconfiguration with the index “X”) may be applied.

Additionally or alternatively, for the (re)transmission(s), in a casethat the configuration of the PUSCH 503 with the index “0” is applied(i.e., in a case that a part of the parameter(s) of the configuration ofthe PUSCH 503 with the index “0” is applied), the configuration of theconfigured grant with the index “0” (i.e., a part of the parameter(s) ofthe configuration of the configured grant with the index “0”) may beapplied. Also, for the (re)transmission(s), in a case that theconfiguration of the PUSCH 503 with the index “1” is applied (i.e., in acase that a part of the parameter(s) of the configuration of the PUSCH503 with the index “1” is applied), the configuration of the configuredgrant with the index “1” (i.e., a part of the parameter(s) of theconfiguration of the configured grant with the index “1”) may beapplied. Also, for the (re)transmission(s), in a case that theconfiguration of the PUSCH 503 with the index “2” is applied (i.e., in acase that a part of the parameter(s) of the configuration of the PUSCH503 with the index “2” is applied), the configuration of the configuredgrant with the index “2” (i.e., a part of the parameter(s) of theconfiguration of the configured grant with the index “2”) may beapplied. Also, for the (re)transmission(s), in a case that theconfiguration of the PUSCH 503 with the index “3” is applied (i.e., in acase that a part of the parameter(s) of the configuration of the PUSCH503 with the index “3” is applied), the configuration of the configuredgrant with the index “3” (i.e., a part of the parameter(s) of theconfiguration of the configured grant with the index “3”) may beapplied.

Also, for the (re)transmission(s), in a case that the configuration ofthe PUSCH 503 linked with the configuration with the index “X” isapplied (i.e., in a case that a part of the parameter(s) of theconfiguration of the PUSCH 503 linked with the configuration with theindex “X” is applied), the configuration with the index “X” (i.e., apart of the parameter(s) of the configuration with the index “X”) may beapplied.

Additionally or alternatively, the single configuration of theconfigured grant and/or the single configuration of the PUSCH 503described herein may be assumed to be included in a single configuration“A” in some implementations for the sake of simple descriptions. Also,the multiple configurations of the configured grant and/or the multipleconfigurations of the PUSCH 503 described herein may be assumed to beincluded in multiple configurations “B” in some implementations for thesake of simple descriptions.

As described above, the information used for indicating the index of theconfiguration of the configured grant may be included in only the DCIformat 0_1 (i.e., the DCI format 0_1 with the CRC scrambled by theCS-RNTI). Namely, the DCI format 0_0 may not include the informationused for indicating the index of the configuration of the configuredgrant.

For example, in a case that the multiple configurations of theconfigured grant are configured, based on the detection (e.g.,detection, decoding) of the DCI format 0_1 with the CRC scrambled by theCS-RNTI (e.g., with the NDI set to “0”), the UE 102 may perform thetransmission corresponding to the configured grant based on the multipleconfigurations “B” (e.g., as described above).

Additionally or alternatively, in a case that the multipleconfigurations of the configured grant, based on the detection of theDCI format 0_1 with the CRC scrambled by the CS-RNTI (e.g., with the NDIset to “1”), the UE 102 may perform the retransmission (e.g., theretransmission of the TB(s)) based on the multiple configurations “B”(e.g., as described above).

Additionally or alternatively, in a case that the DCI format 0_0 withthe CRC scrambled by the CS-RNTI (e.g., with the NDI set to “0”) isdetected, the UE 102 may perform the transmission corresponding to theconfigured grant based on the single configuration “A” (e.g., asdescribed above). Namely, even if the multiple configurations of theconfigured grant are configured, in a case that the DCI format 0_0 withthe CRC scrambled by the CS-RNTI (e.g., with the NDI set to “0”) isdetected, the UE 102 may perform the transmission corresponding to theconfigured grant based on the single configuration “A”.

For example, in a case that the DCI format 0_0 with the CRC scrambled bythe CS-RNTI (e.g., with the NDI set to “0”) is detected, the UE 102 mayperform the transmission corresponding to the configured grant based onthe configuration with the index “X” and/or the configuration of thePUSCH 503 linked with the configuration with the index “X”.

Additionally or alternatively, in a case that the DCI format 0_0 withthe CRC scrambled by the CS-RNTI (e.g., with the NDI set to “1”) isdetected, the UE 102 may perform the retransmission (e.g., theretransmission of the TB(s)) based on the single configuration “A”(e.g., as described above). Namely, even if the multiple configurationsof the configured grant are configured, in a case that the DCI format0_0 with the CRC scrambled by the CS-RNTI (e.g., with the NDI set to“1”) is detected, the UE 102 may perform the retransmission based on thesingle configuration “A”.

For example, in a case that the DCI format 0_0 with the CRC scrambled bythe CS-RNTI (e.g., with the NDI set to “1”) is detected, the UE 102 mayperform the retransmission based on the configuration with the index “X”and/or the configuration of the PUSCH 503 linked with the configurationwith the index “X”.

Additionally or alternatively, in a case that the DCI format(s) (e.g.,the DCI format 0_0 and/or the DCI format 0_1) with the CRC scrambled bythe CS-RNTI (e.g., with the NDI set to “0”) is detected in the CSS(i.e., the CSS set), the UE 102 may perform the transmissioncorresponding to the configured grant based on the single configuration“A” (e.g., as described above). Namely, even if the multipleconfigurations of the configured grant are configured, in a case thatthe DCI format(s) (e.g., the DCI format 0_0 and/or the DCI format 0_1)with the CRC scrambled by the CS-RNTI (e.g., with the NDI set to “0”) isdetected in the CSS, the UE 102 may perform the transmissioncorresponding to the configured grant based on the single configuration“A”. Namely, in a case that the DCI format(s) (e.g., the DCI format 0_0and/or the DCI format 0_1) with the CRC scrambled by the CS-RNTI (e.g.,with the NDI set to “0”) is detected in the USS (i.e., the USS set), theUE 102 may perform the transmission corresponding to the configuredgrant based on the multiple configurations “B” (e.g., as describedabove).

For example, in a case that the DCI format(s) (e.g., the DCI format 0_0and/or the DCI format 0_1) with the CRC scrambled by the CS-RNTI (e.g.,with the NDI set to “0”) is detected in the CSS (i.e., the CSS set), theUE 102 may perform the transmission corresponding to the configuredgrant based on the configuration with the index “X” and/or theconfiguration of the PUSCH 503 linked with the configuration with theindex “X”.

Additionally or alternatively, in a case that the DCI format(s) (e.g.,the DCI format 0_0 and/or the DCI format 0_1) with the CRC scrambled bythe CS-RNTI (e.g., with the NDI set to “0”) is detected in the CSS(i.e., the CSS set), the UE 102 may perform the retransmission (e.g.,the retransmission of the TB(s)) based on the single configuration “A”(e.g., as described above). Namely, even if the multiple configurationsof the configured grant are configured, in a case that the DCI format(s)(e.g., the DCI format 0_0 and/or the DCI format 0_1) with the CRCscrambled by the CS-RNTI (e.g., with the NDI set to “0”) is detected inthe CSS (i.e., the CSS set), the UE 102 may perform the retransmissionbased on the single configuration “A”.

For example, in a case that the DCI format(s) (e.g., the DCI format 0_0and/or the DCI format 0_1) with the CRC scrambled by the CS-RNTI (e.g.,with the NDI set to “0”) is detected in the CSS (i.e., the CSS set), theUE 102 may perform the retransmission based on the configuration withthe index “X” and/or the configuration of the PUSCH 503 linked with theconfiguration with the index “X”.

Additionally or alternatively, in a case that the DCI format(s) (e.g.,the DCI format 0_0 and/or the DCI format 0_1) with the CRC scrambled bythe CS-RNTI (e.g., with the NDI set to “0”) is detected in the CORESET#0, the UE 102 may perform the transmission corresponding to theconfigured grant based on the single configuration “A” (e.g., asdescribed above). Namely, even if the multiple configurations of theconfigured grant are configured, in a case that the DCI format(s) (e.g.,the DCI format 0_0 and/or the DCI format 0_1) with the CRC scrambled bythe CS-RNTI (e.g., with the NDI set to “0”) is detected in the CORESET#0, the UE 102 may perform the transmission corresponding to theconfigured grant based on the single configuration “A”. Namely, in acase that the DCI format(s) (e.g., the DCI format 0_0 and/or the DCIformat 0_1) with the CRC scrambled by the CS-RNTI (e.g., with the NDIset to “0”) is detected in the CORESET(s) other than the CORESET #0, theUE 102 may perform the transmission corresponding to the configuredgrant based on the multiple configurations “B” (e.g., as describedabove).

For example, in a case that the DCI format(s) (e.g., the DCI format 0_0and/or the DCI format 0_1) with the CRC scrambled by the CS-RNTI (e.g.,with the NDI set to “0”) is detected in the CORESET #0, the UE 102 mayperform the transmission corresponding to the configured grant based onthe configuration with the index “X” and/or the configuration of thePUSCH 503 linked with the configuration with the index “X”.

Additionally or alternatively, in a case that the DCI format(s) (e.g.,the DCI format 0_0 and/or the DCI format 0_1) with the CRC scrambled bythe CS-RNTI (e.g., with the NDI set to “0”) is detected in the CORESET#0, the UE 102 may perform the retransmission (e.g., the retransmissionof the TB(s)) based on the single configuration “A” (e.g., as describedabove). Namely, even if the multiple configurations of the configuredgrant are configured, in a case that the DCI format(s) (e.g., the DCIformat 0_0 and/or the DCI format 0_1) with the CRC scrambled by theCS-RNTI (e.g., with the NDI set to “0”) is detected in the CORESET #0,the UE 102 may perform the retransmission based on the singleconfiguration “A”.

For example, in a case that the DCI format(s) (e.g., the DCI format 0_0and/or the DCI format 0_1) with the CRC scrambled by the CS-RNTI (e.g.,with the NDI set to “0”) is detected in the CORESET #0, the UE 102 mayperform the retransmission based on the configuration with the index “X”and/or the configuration of the PUSCH 503 linked with the configurationwith the index “X”.

Additionally or alternatively, in a case that the DCI format(s) (e.g.,the DCI format 0_0 and/or the DCI format 0_1) with the CRC scrambled bythe CS-RNTI (e.g., with the NDI set to “0”) is detected in the searchspace set with the index “0” (i.e., a search space set #0), the UE 102may perform the transmission corresponding to the configured grant basedon the single configuration “A” (e.g., as described above). Namely, evenif the multiple configurations of the configured grant are configured,in a case that the DCI format(s) (e.g., the DCI format 0_0 and/or theDCI format 0_1) with the CRC scrambled by the CS-RNTI (e.g., with theNDI set to “0”) is detected in the search space set #0, the UE 102 mayperform the transmission corresponding to the configured grant based onthe single configuration “A”. Namely, in a case that the DCI format(s)(e.g., the DCI format 0_0 and/or the DCI format 0_1) with the CRCscrambled by the CS-RNTI (e.g., with the NDI set to “0”) is detected inthe search space other than the search space set #0, the UE 102 mayperform the transmission corresponding to the configured grant based onthe multiple configurations “B” (e.g., as described above).

For example, in a case that the DCI format(s) (e.g., the DCI format 0_0and/or the DCI format 0_1) with the CRC scrambled by the CS-RNTI (e.g.,with the NDI set to “0”) is detected in the search space set #0, the UE102 may perform the transmission corresponding to the configured grantbased on the configuration with the index “X” and/or the configurationof the PUSCH 503 linked with the configuration with the index “X”.

Additionally or alternatively, in a case that the DCI format(s) (e.g.,the DCI format 0_0 and/or the DCI format 0_1) with the CRC scrambled bythe CS-RNTI (e.g., with the NDI set to “0”) is detected in the searchspace set #0, the UE 102 may perform the retransmission (e.g., theretransmission of the TB(s)) based on the single configuration “A”(e.g., as described above). Namely, even if the multiple configurationsof the configured grant are configured, in a case that the DCI format(s)(e.g., the DCI format 0_0 and/or the DCI format 0_1) with the CRCscrambled by the CS-RNTI (e.g., with the NDI set to “0”) is detected inthe search space set #0, the UE 102 may perform the retransmission basedon the single configuration “A”.

For example, in a case that the DCI format(s) (e.g., the DCI format 0_0and/or the DCI format 0_1) with the CRC scrambled by the CS-RNTI (e.g.,with the NDI set to “0”) is detected in the search space set #0, the UE102 may perform the retransmission based on the configuration with theindex “X” and/or the configuration of the PUSCH 503 linked with theconfiguration with the index “X”.

Also, a grouping of the configuration(s) of the configured grant may besupported. For example, the gNB 160 may transmit, by using the RRCmessage, information used for configuring a correspondence of aconfigured grant configuration group (e.g., a configured grantconfiguration group with an index) and the configuration(s) of theconfigured grant (e.g., the configuration(s) of the configured grantwith an index). For example, the configuration of the configured grantwith the index “0” may be corresponding to the configured grantconfiguration group with the index “0”. Also, the configuration of theconfigured grant with the index “1” may be corresponding to theconfigured grant configuration group with the index “1”. Also, theconfiguration of the configured grant with the index “2” may becorresponding to the configured grant configuration group with the index“0”. Namely, the configuration of the configured grant with the index“0” and the configuration of the configured grant with the index “2” maybelong to the same group (i.e., the configured grant configuration group“0”). Also, the configuration of the configured grant with the index “4”may be corresponding to the configured grant configuration group withthe index “1”. Namely, the configuration of the configured grant withthe index “1” and the configuration of the configured grant with theindex “4” may belong to the same group (i.e., the configured grantconfiguration group “1”).

Also, a grouping of the configuration(s) of the PUSCH may be supported.For example, the gNB 160 may transmit, by using the RRC message,information used for configuring a correspondence of a PUSCHconfiguration group (e.g., a PUSCH configuration group with an index)and the configuration(s) of the PUSCH (e.g., the configuration(s) of thePUSCH with an index). For example, the configuration of the PUSCH withthe index “0” may be corresponding to the PUSCH configuration group withthe index “1”. Also, the configuration of the PUSCH with the index “1”may be corresponding to the PUSCH configuration group with the index“0”. Also, the configuration of the PUSCH with the index “2” may becorresponding to the PUSCH configuration group with the index “0”.Namely, the configuration of the PUSCH with the index “1” and theconfiguration of the PUSCH with the index “2” may belong to the samegroup (i.e., the PUSCH configuration group “0”). Also, the configurationof the PUSCH with the index “3” may be corresponding to the PUSCHconfiguration group with the index “1”. Namely, the configuration of thePUSCH with the index “0” and the configuration of the PUSCH with theindex “3” may belong to the same group (i.e., the PUSCH configurationgroup “1”).

Namely, in the systems and methods disclosed herein, theconfiguration(s) of the configured grant (e.g., the configuration of theconfigured grant with the index) may be replaced by the configured grantconfiguration group (e.g., the configured grant configured group withthe index). Here, the configured grant configuration group may includeone or more configurations of the configured grant (e.g., one or moreconfigurations of the configured grant with the index). For example, theconfiguration(s) of the configured grant with the index “X” may bereplaced by the configured grant configuration group with the index “X”.

Also, in the systems and methods disclosed herein, the configuration(s)of the PUSCH (e.g., the configuration(s) of the PUSCH with the index)may be replaced by the PUSCH configuration group (e.g., the PUSCHconfiguration group with the index). Here, the PUSCH configuration groupmay include one or more PUSCH configurations (e.g., one or more PUSCHconfigurations with the index).

Some parameters may be common among different configured grantconfigurations. Namely, some parameters may be shared by multipleconfigured grants. The common or shared parameters may befrequencyHopping, cg-DMRS-Configuration, mcs-Table,mcs-TableTransformPrecoder, uci-OnPUSCH, resourceAllocation, rbg-Size,powerControlLoopToUse, p0-PUSCH-Alpha, transformPrecoder,nrofHARQ-Processes, repK, repK-RV, periodicity, timeDomainOffset,timeDomainAllocation, frequencyDomainAllocation, antennaPort,dmrs-SeqInitialization, precodingAndNumberOfLayers,srs-ResourceIndicator, mcsAndTBS, frequencyHoppingOffset,pathlossReferenceIndex, CG-UCI-OnPUSCH, pusch-TimeDomainAllocationList,set of repetition numbers, dynamic repetition number enabler or anycombination of above.

For example, an RRC message may include a common configuration (e.g.,ConfiguredGrantConfig-common IE). The ConfiguredGrantConfig-common IEmay include the common or shared parameters mentioned above. When one ormore configured grants are configured, parameter(s) in theConfiguredGrantConfig-common IE may or may not be applied to thecorresponding configured grant(s). If the corresponding one or moreparameters are not included in a specific configured grant configuration(e.g., ConfiguredGrantConfig IE), the specific configured grant mayfollow and/or apply the one or more parameter included in the commonconfiguration (e.g., ConfiguredGrantConfig-common IE).

Some parameters may be configured in both a common configuration (e.g.,ConfiguredGrantConfig-common IE) and a specific configured grantconfiguration (e.g., ConfiguredGrantConfig). In a design, parameter(s)in the specific configured grant configuration may overwrite theparameter(s) in the ConfiguredGrantConfig-common IE. Namely, configuredvalue(s) of parameter(s) in the specific configured grant configurationmay be applied to the corresponding configured grant(s) even if the sameparameter(s) may be already configured in the common configuration(e.g., ConfiguredGrantConfig-common IE).

In yet another design, parameter(s) in the ConfiguredGrantConfig-commonIE may overwrite the parameter(s) in the specific configured grantconfiguration. Namely, configured value(s) of parameter(s) in the commonconfiguration (e.g., ConfiguredGrantConfig-common IE) may be applied tothe corresponding configured grant(s) no matter whether the sameparameter(s) are already configured in the specific configured grantconfiguration (e.g., ConfiguredGrantConfig IE) or not.

In yet another design, for configured grant Type 2, in a case that theDCI format(s) (e.g., the DCI format 0_0 and/or the DCI format 0_1) withthe CRC scrambled by the CS-RNTI (e.g., with the NDI set to “0”) isdetected in the CSS (i.e., the CSS set), the UE 102 may perform thetransmission corresponding to the configured grant based on parameter(s)in the ConfiguredGrantConfig-common IE. Namely, even if some parametersfor the one or multiple configurations of the configured grant areconfigured by specific configuration (e.g., ConfiguredGrantConfig IE),in a case that the DCI format(s) (e.g., the DCI format 0_0 and/or theDCI format 0_1) with the CRC scrambled by the CS-RNTI (e.g., with theNDI set to “0”) is detected in the CSS, the UE 102 may perform thetransmission corresponding to the configured grant based on parameter(s)in the ConfiguredGrantConfig-common IE. Namely, in a case that the DCIformat(s) (e.g., the DCI format 0_0 and/or the DCI format 0_1) with theCRC scrambled by the CS-RNTI (e.g., with the NDI set to “0”) is detectedin the USS (i.e., the USS set), the UE 102 may perform the transmissioncorresponding to the configured grant based on the parameters in thespecific configuration (e.g., ConfiguredGrantConfig IE).

In yet another design, in a case that the DCI format(s) (e.g., the DCIformat 0_0 and/or the DCI format 0_1) with the CRC scrambled by theCS-RNTI (e.g., with the NDI set to “1”) is detected in the CSS (i.e.,the CSS set), the UE 102 may perform the retransmission corresponding tothe configured grant based on parameter(s) in theConfiguredGrantConfig-common IE. Namely, even if some parameters for theone or multiple configurations of the configured grant are configured byspecific configuration (e.g., ConfiguredGrantConfig IE), in a case thatthe DCI format(s) (e.g., the DCI format 0_0 and/or the DCI format 0_1)with the CRC scrambled by the CS-RNTI (e.g., with the NDI set to “1”) isdetected in the CSS, the UE 102 may perform the retransmissioncorresponding to the configured grant based on parameter(s) in theConfiguredGrantConfig-common IE. Namely, in a case that the DCIformat(s) (e.g., the DCI format 0_0 and/or the DCI format 0_1) with theCRC scrambled by the CS-RNTI (e.g., with the NDI set to “1”) is detectedin the USS (i.e., the USS set), the UE 102 may perform theretransmission corresponding to the configured grant based on theparameters in the specific configuration (e.g., ConfiguredGrantConfigIE).

In yet another design, for configured grant Type 2, in a case that theDCI format(s) (e.g., the DCI format 0_0 and/or the DCI format 0_1) withthe CRC scrambled by the CS-RNTI (e.g., with the NDI set to “0”) isdetected in the CORESET #0, the UE 102 may perform the transmissioncorresponding to the configured grant based on parameter(s) in theConfiguredGrantConfig-common IE. Namely, even if some parameters for theone or multiple configurations of the configured grant are configured byspecific configuration (e.g., ConfiguredGrantConfig IE), in a case thatthe DCI format(s) (e.g., the DCI format 0_0 and/or the DCI format 0_1)with the CRC scrambled by the CS-RNTI (e.g., with the NDI set to “0”) isdetected in the CORESET #0, the UE 102 may perform the transmissioncorresponding to the configured grant based on parameter(s) in theConfiguredGrantConfig-common IE. Namely, in a case that the DCIformat(s) (e.g., the DCI format 0_0 and/or the DCI format 0_1) with theCRC scrambled by the CS-RNTI (e.g., with the NDI set to “0”) is detectedin the CORESET(s) other than the CORESET #0, the UE 102 may perform thetransmission corresponding to the configured grant based on theparameters in the specific configuration (e.g., ConfiguredGrantConfigIE).

In yet another design, in a case that the DCI format(s) (e.g., the DCIformat 0_0 and/or the DCI format 0_1) with the CRC scrambled by theCS-RNTI (e.g., with the NDI set to “1”) is detected in the CORESET #0,the UE 102 may perform the retransmission corresponding to theconfigured grant based on parameter(s) in theConfiguredGrantConfig-common IE. Namely, even if some parameters for theone or multiple configurations of the configured grant are configured byspecific configuration (e.g., ConfiguredGrantConfig IE), in a case thatthe DCI format(s) (e.g., the DCI format 0_0 and/or the DCI format 0_1)with the CRC scrambled by the CS-RNTI (e.g., with the NDI set to “1”) isdetected in the CORESET #0, the UE 102 may perform the retransmissioncorresponding to the configured grant based on parameter(s) in theConfiguredGrantConfig-common IE. Namely, in a case that the DCIformat(s) (e.g., the DCI format 0_0 and/or the DCI format 0_1) with theCRC scrambled by the CS-RNTI (e.g., with the NDI set to “1”) is detectedin the CORESET(s) other than the CORESET #0, the UE 102 may perform theretransmission corresponding to the configured grant based on theparameters in the specific configuration (e.g., ConfiguredGrantConfigIE).

In yet another design, for configured grant Type 2, in a case that theDCI format(s) (e.g., the DCI format 0_0 and/or the DCI format 0_1) withthe CRC scrambled by the CS-RNTI (e.g., with the NDI set to “0”) isdetected in the search space set with the index “0” (i.e., a searchspace set #0), the UE 102 may perform the transmission corresponding tothe configured grant based on parameter(s) in theConfiguredGrantConfig-common IE. Namely, even if some parameters for theone or multiple configurations of the configured grant are configured byspecific configuration (e.g., ConfiguredGrantConfig IE), in a case thatthe DCI format(s) (e.g., the DCI format 0_0 and/or the DCI format 0_1)with the CRC scrambled by the CS-RNTI (e.g., with the NDI set to “0”) isdetected in the search space set with the index “0” (i.e., a searchspace set #0), the UE 102 may perform the transmission corresponding tothe configured grant based on parameter(s) in theConfiguredGrantConfig-common IE. Namely, in a case that the DCIformat(s) (e.g., the DCI format 0_0 and/or the DCI format 0_1) with theCRC scrambled by the CS-RNTI (e.g., with the NDI set to “0”) is detectedin the search space other than the search space set #0, the UE 102 mayperform the transmission corresponding to the configured grant based onthe parameters in the specific configuration (e.g.,ConfiguredGrantConfig IE).

In yet another design, in a case that the DCI format(s) (e.g., the DCIformat 0_0 and/or the DCI format 0_1) with the CRC scrambled by theCS-RNTI (e.g., with the NDI set to “1”) is detected in the search spaceset with the index “0” (i.e., a search space set #0), the UE 102 mayperform the retransmission corresponding to the configured grant basedon parameter(s) in the ConfiguredGrantConfig-common IE. Namely, even ifsome parameters for the one or multiple configurations of the configuredgrant are configured by specific configuration (e.g.,ConfiguredGrantConfig IE), in a case that the DCI format(s) (e.g., theDCI format 0_0 and/or the DCI format 0_1) with the CRC scrambled by theCS-RNTI (e.g., with the NDI set to “0”) is detected in the search spaceset with the index “1” (i.e., a search space set #0), the UE 102 mayperform the retransmission corresponding to the configured grant basedon parameter(s) in the ConfiguredGrantConfig-common IE. Namely, in acase that the DCI format(s) (e.g., the DCI format 0_0 and/or the DCIformat 0_1) with the CRC scrambled by the CS-RNTI (e.g., with the NDIset to “1”) is detected in the search space other than the search spaceset #0, the UE 102 may perform the retransmission corresponding to theconfigured grant based on the parameters in the specific configuration(e.g., ConfiguredGrantConfig IE).

In yet another example, the common or shared parameters mentioned abovemay be included in a configuration for a specific configured grant(e.g., configured grant with an index “a predetermined value (e.g., 0)”,ConfiguredGrantConfig IE with configuration index 0), which is referredto as a primary configured grant. Other configured grant(s) (e.g.,configured grant(s) with an index other than “a predetermined value(e.g., 0)”), which is referred to as a secondary configured grant(s),may follow and/or apply the common or shared parameters included in theconfiguration for the primary configured grant. If the corresponding oneor more parameters are not included in a configured grant configurationother than the primary configured grant configuration (e.g., aconfigured grant configuration with an index “X” except for the index“the predetermined value”), the configured grant configuration otherthan the primary configured grant may apply and/or follow the one ormore parameters included in the configuration for the primary configuredgrant (e.g., configured grant configuration with an index “apredetermined value (e.g., 0)”).

Some parameters may be configured in both the primary configured grantconfiguration (e.g., configured grant with an index “a predeterminedvalue (e.g., 0)”, ConfiguredGrantConfig IE with configuration index 0)and the secondary configured grant configuration (e.g., configuredgrant(s) with an index other than “a predetermined value (e.g., 0)”). Ina design, parameter(s) in the primary configured grant configuration mayoverwrite the parameter(s) in the secondary configured grantconfiguration. Namely, configured value(s) of parameter(s) in theprimary configured grant configuration may be applied to the secondaryconfigured grant(s) even if the same parameter(s) may be alreadyconfigured in the secondary configured grant configuration.

In yet another design, parameter(s) in the secondary configured grantconfiguration may overwrite the parameter(s) in the primary configuredgrant configuration. Namely, configured value(s) of parameter(s) in thesecondary configured grant configuration may be applied to the secondaryconfigured grant(s) no matter whether the same parameter(s) may bealready configured in the primary configured grant configuration (e.g.,ConfiguredGrantConfig IE) or not.

In yet another design, for configured grant Type 2, in a case that theDCI format(s) (e.g., the DCI format 0_0 and/or the DCI format 0_1) withthe CRC scrambled by the CS-RNTI (e.g., with the NDI set to “0”) isdetected in the CSS (i.e., the CSS set), the UE 102 may perform thetransmission corresponding to the secondary configured grant (e.g.,configured grant(s) with an index other than “a predetermined value(e.g., 0)”) based on parameter(s) in the primary configured grantconfiguration (e.g., configured grant with an index “a predeterminedvalue (e.g., 0)”, ConfiguredGrantConfig IE with configuration index 0).Namely, even if some parameters for the secondary configured grant areconfigured by the secondary configured grant configuration, in a casethat the DCI format(s) (e.g., the DCI format 0_0 and/or the DCI format0_1) with the CRC scrambled by the CS-RNTI (e.g., with the NDI set to“0”) is detected in the CSS, the UE 102 may perform the transmissioncorresponding to the secondary configured grant based on parameter(s) inthe primary configured grant configuration. Namely, in a case that theDCI format(s) (e.g., the DCI format 0_0 and/or the DCI format 0_1) withthe CRC scrambled by the CS-RNTI (e.g., with the NDI set to “0”) isdetected in the USS (i.e., the USS set), the UE 102 may perform thetransmission corresponding to the secondary configured grant based onthe parameters in the secondary configured grant configuration.

In yet another design, in a case that the DCI format(s) (e.g., the DCIformat 0_0 and/or the DCI format 0_1) with the CRC scrambled by theCS-RNTI (e.g., with the NDI set to “1”) is detected in the CSS (i.e.,the CSS set), the UE 102 may perform the retransmission corresponding tothe secondary configured grant (e.g., configured grant(s) with an indexother than “a predetermined value (e.g., 0)”) based on parameter(s) inthe primary configured grant configuration (e.g., configured grant withan index “a predetermined value (e.g., 0)”, ConfiguredGrantConfig IEwith configuration index 0). Namely, even if some parameters for thesecondary configured grant are configured by the secondary configuredgrant configuration, in a case that the DCI format(s) (e.g., the DCIformat 0_0 and/or the DCI format 0_1) with the CRC scrambled by theCS-RNTI (e.g., with the NDI set to “1”) is detected in the CSS, the UE102 may perform the retransmission corresponding to the secondaryconfigured grant based on parameter(s) in the primary configured grantconfiguration. Namely, in a case that the DCI format(s) (e.g., the DCIformat 0_0 and/or the DCI format 0_1) with the CRC scrambled by theCS-RNTI (e.g., with the NDI set to “1”) is detected in the USS (i.e.,the USS set), the UE 102 may perform the retransmission corresponding tothe secondary configured grant based on the parameters in the secondaryconfigured grant configuration.

In yet another design, for configured grant Type 2, in a case that theDCI format(s) (e.g., the DCI format 0_0 and/or the DCI format 0_1) withthe CRC scrambled by the CS-RNTI (e.g., with the NDI set to “0”) isdetected in the CORESET #0, the UE 102 may perform the transmissioncorresponding to the secondary configured grant (e.g., configuredgrant(s) with an index other than “a predetermined value (e.g., 0)”)based on parameter(s) in the primary configured grant configuration(e.g., configured grant with an index “a predetermined value (e.g., 0)”,ConfiguredGrantConfig IE with configuration index 0). Namely, even ifsome parameters for the secondary configured grant are configured by thesecondary configured grant configuration, in a case that the DCIformat(s) (e.g., the DCI format 0_0 and/or the DCI format 0_1) with theCRC scrambled by the CS-RNTI (e.g., with the NDI set to “0”) is detectedin the CORESET #0, the UE 102 may perform the transmission correspondingto the secondary configured grant based on parameter(s) in the primaryconfigured grant configuration. Namely, in a case that the DCI format(s)(e.g., the DCI format 0_0 and/or the DCI format 0_1) with the CRCscrambled by the CS-RNTI (e.g., with the NDI set to “0”) is detected inthe CORESET(s) other than the CORESET #0, the UE 102 may perform thetransmission corresponding to the secondary configured grant based onthe parameters in the secondary configured grant configuration.

In yet another design, in a case that the DCI format(s) (e.g., the DCIformat 0_0 and/or the DCI format 0_1) with the CRC scrambled by theCS-RNTI (e.g., with the NDI set to “1”) is detected in the CORESET #0,the UE 102 may perform the retransmission corresponding to the secondaryconfigured grant (e.g., configured grant(s) with an index other than “apredetermined value (e.g., 0)”) based on parameter(s) in the primaryconfigured grant configuration (e.g., configured grant with an index “apredetermined value (e.g., 0)”, ConfiguredGrantConfig IE withconfiguration index 0). Namely, even if some parameters for thesecondary configured grant are configured by the secondary configuredgrant configuration, in a case that the DCI format(s) (e.g., the DCIformat 0_0 and/or the DCI format 0_1) with the CRC scrambled by theCS-RNTI (e.g., with the NDI set to “1”) is detected in the CORESET #0,the UE 102 may perform the retransmission corresponding to the secondaryconfigured grant based on parameter(s) in the primary configured grantconfiguration. Namely, in a case that the DCI format(s) (e.g., the DCIformat 0_0 and/or the DCI format 0_1) with the CRC scrambled by theCS-RNTI (e.g., with the NDI set to “1”) is detected in the CORESET(s)other than the CORESET #0, the UE 102 may perform the retransmissioncorresponding to the secondary configured grant based on the parametersin the secondary configured grant configuration.

In yet another design, for configured grant Type 2, in a case that theDCI format(s) (e.g., the DCI format 0_0 and/or the DCI format 0_1) withthe CRC scrambled by the CS-RNTI (e.g., with the NDI set to “0”) isdetected in the search space set with the index “0” (i.e., a searchspace set #0), the UE 102 may perform the transmission corresponding tothe secondary configured grant (e.g., configured grant(s) with an indexother than “a predetermined value (e.g., 0)”) based on parameter(s) inthe primary configured grant configuration (e.g., configured grant withan index “a predetermined value (e.g., 0)”, ConfiguredGrantConfig IEwith configuration index 0). Namely, even if some parameters for thesecondary configured grant are configured by the secondary configuredgrant configuration, in a case that the DCI format(s) (e.g., the DCIformat 0_0 and/or the DCI format 0_1) with the CRC scrambled by theCS-RNTI (e.g., with the NDI set to “0”) is detected in the search spaceset with the index “0” (i.e., a search space set #0), the UE 102 mayperform the transmission corresponding to the secondary configured grantbased on parameter(s) in the primary configured grant configuration.Namely, in a case that the DCI format(s) (e.g., the DCI format 0_0and/or the DCI format 0_1) with the CRC scrambled by the CS-RNTI (e.g.,with the NDI set to “0”) is detected in the search space other than thesearch space set #0, the UE 102 may perform the transmissioncorresponding to the secondary configured grant based on the parametersin the secondary configured grant configuration.

In yet another design, in a case that the DCI format(s) (e.g., the DCIformat 0_0 and/or the DCI format 0_1) with the CRC scrambled by theCS-RNTI (e.g., with the NDI set to “0”) is detected in the search spaceset with the index “1” (i.e., a search space set #0), the UE 102 mayperform the retransmission corresponding to the secondary configuredgrant (e.g., configured grant(s) with an index other than “apredetermined value (e.g., 0)”) based on parameter(s) in the primaryconfigured grant configuration (e.g., configured grant with an index “apredetermined value (e.g., 0)”, ConfiguredGrantConfig IE withconfiguration index 0). Namely, even if some parameters for thesecondary configured grant are configured by the secondary configuredgrant configuration, in a case that the DCI format(s) (e.g., the DCIformat 0_0 and/or the DCI format 0_1) with the CRC scrambled by theCS-RNTI (e.g., with the NDI set to “1”) is detected in the search spaceset with the index “0” (i.e., a search space set #0), the UE 102 mayperform the retransmission corresponding to the secondary configuredgrant based on parameter(s) in the primary configured grantconfiguration. Namely, in a case that the DCI format(s) (e.g., the DCIformat 0_0 and/or the DCI format 0_1) with the CRC scrambled by theCS-RNTI (e.g., with the NDI set to “1”) is detected in the search spaceother than the search space set #0, the UE 102 may perform theretransmission corresponding to the secondary configured grant based onthe parameters in the secondary configured grant configuration.

Mini-slot repetitions and/or multi-segment transmissions may also besupported for configured grant and/or grant-based PUSCH transmission.Mini-slot repetitions and/or multi-segment transmissions may be enabledand/or configured commonly or separately for each configured grantand/or each PUSCH configuration.

For example, one or more actual PUSCH repetitions in one slot, or two ormore actual PUSCH repetitions across slot boundary in consecutiveavailable slots, may be supported using one UL grant for dynamic PUSCH,and one configured grant configuration for configured grant PUSCH byOption-A. The number of the repetitions signaled (dynamically signaled,e.g., DCI indicated, or semi-statically signaled, e.g., RRC configured,or combination of them) by gNB 160 may represent the “nominal” number ofrepetitions. The actual number of repetitions can be larger than thenominal number. The time domain resource assignment (TDRA) field in theDCI or the TDRA parameter in the type 1 configured grant indicates theresource for the first “nominal” repetition. The time domain resourcesfor the remaining repetitions are derived based at least on theresources for the first repetition and the UL/DL direction of thesymbols. If a “nominal” repetition (transmission occasion) goes acrossthe slot boundary or DL/UL switching point, this “nominal” repetition(transmission occasion) is split into multiple PUSCH repetitions(transmission occasions), with one PUSCH repetition (transmissionoccasion) in each UL period in a slot. In a case that multipleconfigurations of configured grants and/or multiple configurations ofPUSCH transmissions are supported, Option-A may be configured and/orenabled for each configured grant configuration and/or each PUSCHtransmission configuration separately or commonly. One or more newtables of TDRA may be introduced for Option-A. The new table(s) of TDRAmay be fixed by specification (e.g., a defaulted table). The newtable(s) of TDRA may be RRC configured. The new table(s) of TDRA may becommonly configured for multiple configurations of configured grantsand/or multiple configurations of PUSCH transmissions. The new table(s)of TDRA may be configured and/or enabled for each configured grantconfiguration and/or each PUSCH transmission configuration separately.How to determine the table of TDRA may follow the same procedures asother parameter determination described above.

In yet another example, one or more PUSCH repetitions in one slot, ortwo or more PUSCH repetitions across slot boundary in consecutiveavailable slots, are supported using one UL grant for dynamic PUSCH, andone configured grant configuration for configured grant PUSCH byOption-B. The time domain resource assignment (TDRA) field in the DCI orthe TDRA parameter in the type 1 configured grant indicates an entry inthe higher layer configured table. The number of repetitions, startingsymbols of each repetition, length of each repetition, and mapping ofthe repetitions to slots can be obtained from each entry in the table.More than one repetition can be mapped to one slot. The resourceassignment for each repetition is contained within one slot. Eachtransmitted repetition is contained within one UL period in a slot. In acase that multiple configurations of configured grants and/or multipleconfigurations of PUSCH transmissions are supported, Option-B may beconfigured and/or enabled for each configured grant configuration and/oreach PUSCH transmission configuration separately or commonly. One ormore new tables of TDRA may be introduced for Option-B. The new table(s)of TDRA may be fixed by specification (e.g., a defaulted table). The newtable(s) of TDRA may be RRC configured. The new table(s) of TDRA may becommonly configured for multiple configurations of configured grantsand/or multiple configurations of PUSCH transmissions. The new table(s)of TDRA may be configured and/or enabled for each configured grantconfiguration and/or each PUSCH transmission configuration separately.How to determine the table of TDRA may follow the same procedures asother parameter determination described above.

Option-A and Option-B may be supported simultaneously. For example,Option-A may be enabled and/or configured for one of multipleconfigurations while Option-B may be enabled and/or configured foranother one of multiple configurations. In yet another example, Option-A(or Option-B) may be enabled and/or configured for configured grantwhile Option-B (or Option-A) may be enabled and/or configured forgrant-based PUSCH. In yet another example, Option-A (or Option-B) may beenabled and/or configured for configured grant Type 1 while Option-B (orOption-A) may be enabled and/or configured for configured grant Type 2.

FIG. 6 illustrates various components that may be utilized in a UE 602.The UE 602 described in connection with FIG. 6 may be implemented inaccordance with the UE 102 described in connection with FIG. 1. The UE602 includes a processor 603 that controls operation of the UE 602. Theprocessor 603 may also be referred to as a central processing unit(CPU). Memory 605, which may include read-only memory (ROM), randomaccess memory (RAM), a combination of the two or any type of device thatmay store information, provides instructions 607 a and data 609 a to theprocessor 603. A portion of the memory 605 may also include non-volatilerandom access memory (NVRAM). Instructions 607 b and data 609 b may alsoreside in the processor 603. Instructions 607 b and/or data 609 b loadedinto the processor 603 may also include instructions 607 a and/or data609 a from memory 605 that were loaded for execution or processing bythe processor 603. The instructions 607 b may be executed by theprocessor 603 to implement the methods described herein.

The UE 602 may also include a housing that contains one or moretransmitters 658 and one or more receivers 620 to allow transmission andreception of data. The transmitter(s) 658 and receiver(s) 620 may becombined into one or more transceivers 618. One or more antennas 622 a-nare attached to the housing and electrically coupled to the transceiver618.

The various components of the UE 602 are coupled together by a bussystem 611, which may include a power bus, a control signal bus and astatus signal bus, in addition to a data bus. However, for the sake ofclarity, the various buses are illustrated in FIG. 6 as the bus system611. The UE 602 may also include a digital signal processor (DSP) 613for use in processing signals. The UE 602 may also include acommunications interface 615 that provides user access to the functionsof the UE 602. The UE 602 illustrated in FIG. 6 is a functional blockdiagram rather than a listing of specific components.

FIG. 7 illustrates various components that may be utilized in a gNB 760.The gNB 760 described in connection with FIG. 7 may be implemented inaccordance with the gNB 160 described in connection with FIG. 1. The gNB760 includes a processor 703 that controls operation of the gNB 760. Theprocessor 703 may also be referred to as a central processing unit(CPU). Memory 705, which may include read-only memory (ROM), randomaccess memory (RAM), a combination of the two or any type of device thatmay store information, provides instructions 707 a and data 709 a to theprocessor 703. A portion of the memory 705 may also include non-volatilerandom access memory (NVRAM). Instructions 707 b and data 709 b may alsoreside in the processor 703. Instructions 707 b and/or data 709 b loadedinto the processor 703 may also include instructions 707 a and/or data709 a from memory 705 that were loaded for execution or processing bythe processor 703. The instructions 707 b may be executed by theprocessor 703 to implement the methods described herein.

The gNB 760 may also include a housing that contains one or moretransmitters 717 and one or more receivers 778 to allow transmission andreception of data. The transmitter(s) 717 and receiver(s) 778 may becombined into one or more transceivers 776. One or more antennas 780 a-nare attached to the housing and electrically coupled to the transceiver776.

The various components of the gNB 760 are coupled together by a bussystem 711, which may include a power bus, a control signal bus and astatus signal bus, in addition to a data bus. However, for the sake ofclarity, the various buses are illustrated in FIG. 7 as the bus system711. The gNB 760 may also include a digital signal processor (DSP) 713for use in processing signals. The gNB 760 may also include acommunications interface 715 that provides user access to the functionsof the gNB 760. The gNB 760 illustrated in FIG. 7 is a functional blockdiagram rather than a listing of specific components.

FIG. 8 is a block diagram illustrating one implementation of a UE 802 inwhich one or more of the systems and/or methods described herein may beimplemented. The UE 802 includes transmit means 858, receive means 820and control means 824. The transmit means 858, receive means 820 andcontrol means 824 may be configured to perform one or more of thefunctions described in connection with FIG. 1 above. FIG. 6 aboveillustrates one example of a concrete apparatus structure of FIG. 8.Other various structures may be implemented to realize one or more ofthe functions of FIG. 1. For example, a DSP may be realized by software.

FIG. 9 is a block diagram illustrating one implementation of a gNB 960in which one or more of the systems and/or methods described herein maybe implemented. The gNB 960 includes transmit means 917, receive means978 and control means 982. The transmit means 917, receive means 978 andcontrol means 982 may be configured to perform one or more of thefunctions described in connection with FIG. 1 above. FIG. 7 aboveillustrates one example of a concrete apparatus structure of FIG. 9.Other various structures may be implemented to realize one or more ofthe functions of FIG. 1. For example, a DSP may be realized by software.

FIG. 10 is a block diagram illustrating one implementation of a gNB1060. The gNB 1060 may be an example of the gNB 160 described inconnection with FIG. 1. The gNB 1060 may include a higher layerprocessor 1023, a DL transmitter 1025, a UL receiver 1033, and one ormore antenna 1031. The DL transmitter 1025 may include a PDCCHtransmitter 1027 and a PDSCH transmitter 1029. The UL receiver 1033 mayinclude a PUCCH receiver 1035 and a PUSCH receiver 1037.

The higher layer processor 1023 may manage physical layer's behaviors(the DL transmitter's and the UL receiver's behaviors) and providehigher layer parameters to the physical layer. The higher layerprocessor 1023 may obtain transport blocks from the physical layer. Thehigher layer processor 1023 may send/acquire higher layer messages suchas an RRC message and MAC message to/from a UE's higher layer. Thehigher layer processor 1023 may provide the PDSCH transmitter transportblocks and provide the PDCCH transmitter transmission parameters relatedto the transport blocks.

The DL transmitter 1025 may multiplex downlink physical channels anddownlink physical signals (including reservation signal) and transmitthem via transmission antennas 1031. The UL receiver 1033 may receivemultiplexed uplink physical channels and uplink physical signals viareceiving antennas 1031 and de-multiplex them. The PUCCH receiver 1035may provide the higher layer processor 1023 UCI. The PUSCH receiver 1037may provide the higher layer processor 1023 received transport blocks.

FIG. 11 is a block diagram illustrating one implementation of a UE 1102.The UE 1102 may be an example of the UE 102 described in connection withFIG. 1. The UE 1102 may include a higher layer processor 1123, a ULtransmitter 1151, a DL receiver 1143, and one or more antenna 1131. TheUL transmitter 1151 may include a PUCCH transmitter 1153 and a PUSCHtransmitter 1155. The DL receiver 1143 may include a PDCCH receiver 1145and a PDSCH receiver 1147.

The higher layer processor 1123 may manage physical layer's behaviors(the UL transmitter's and the DL receiver's behaviors) and providehigher layer parameters to the physical layer. The higher layerprocessor 1123 may obtain transport blocks from the physical layer. Thehigher layer processor 1123 may send/acquire higher layer messages suchas an RRC message and MAC message to/from a UE's higher layer. Thehigher layer processor 1123 may provide the PUSCH transmitter transportblocks and provide the PUCCH transmitter 1153 UCI.

The DL receiver 1143 may receive multiplexed downlink physical channelsand downlink physical signals via receiving antennas 1131 andde-multiplex them. The PDCCH receiver 1145 may provide the higher layerprocessor 1123 DCI. The PDSCH receiver 1147 may provide the higher layerprocessor 1123 received transport blocks.

As described herein, some methods for the DL and/or UL transmissions maybe applied (e.g., specified). Here, the combination of one or more ofthe some methods described herein may be applied for the DL and/or ULtransmission. The combination of the one or more of the some methodsdescribed herein may not be precluded in the described systems andmethods.

It should be noted that names of physical channels described herein areexamples. The other names such as “NRPDCCH, NRPDSCH, NRPUCCH andNRPUSCH,” “new Generation-(G)PDCCH, GPDSCH, GPUCCH and GPUSCH” or thelike can be used.

The term “computer-readable medium” refers to any available medium thatcan be accessed by a computer or a processor. The term“computer-readable medium,” as used herein, may denote a computer-and/or processor-readable medium that is non-transitory and tangible. Byway of example and not limitation, a computer-readable orprocessor-readable medium may include RAM, ROM, EEPROM, CD-ROM or otheroptical disk storage, magnetic disk storage or other magnetic storagedevices, or any other medium that can be used to carry or store desiredprogram code in the form of instructions or data structures and that canbe accessed by a computer or processor. Disk and disc, as used herein,includes compact disc (CD), laser disc, optical disc, digital versatiledisc (DVD), floppy disk and Blu-ray® disc where disks usually reproducedata magnetically, while discs reproduce data optically with lasers.

It should be noted that one or more of the methods described herein maybe implemented in and/or performed using hardware. For example, one ormore of the methods described herein may be implemented in and/orrealized using a chipset, an application-specific integrated circuit(ASIC), a large-scale integrated circuit (LSI) or integrated circuit,etc.

Each of the methods disclosed herein includes one or more steps oractions for achieving the described method. The method steps and/oractions may be interchanged with one another and/or combined into asingle step without departing from the scope of the claims. In otherwords, unless a specific order of steps or actions is required forproper operation of the method that is being described, the order and/oruse of specific steps and/or actions may be modified without departingfrom the scope of the claims.

It is to be understood that the claims are not limited to the preciseconfiguration and components illustrated above. Various modifications,changes and variations may be made in the arrangement, operation anddetails of the systems, methods and apparatus described herein withoutdeparting from the scope of the claims.

A program running on the gNB 160 or the UE 102 according to thedescribed systems and methods is a program (a program for causing acomputer to operate) that controls a CPU and the like in such a manneras to realize the function according to the described systems andmethods. Then, the information that is handled in these apparatuses istemporarily stored in a RAM while being processed. Thereafter, theinformation is stored in various ROMs or HDDs, and whenever necessary,is read by the CPU to be modified or written. As a recording medium onwhich the program is stored, among a semiconductor (for example, a ROM,a nonvolatile memory card, and the like), an optical storage medium (forexample, a DVD, a MO, a MD, a CD, a BD and the like), a magnetic storagemedium (for example, a magnetic tape, a flexible disk and the like) andthe like, any one may be possible. Furthermore, in some cases, thefunction according to the described systems and methods described hereinis realized by running the loaded program, and in addition, the functionaccording to the described systems and methods is realized inconjunction with an operating system or other application programs,based on an instruction from the program.

Furthermore, in a case where the programs are available on the market,the program stored on a portable recording medium can be distributed orthe program can be transmitted to a server computer that connectsthrough a network such as the Internet. In this case, a storage devicein the server computer also is included. Furthermore, some or all of thegNB 160 and the UE 102 according to the systems and methods describedherein may be realized as an LSI that is a typical integrated circuit.Each functional block of the gNB 160 and the UE 102 may be individuallybuilt into a chip, and some or all functional blocks may be integratedinto a chip. Furthermore, a technique of the integrated circuit is notlimited to the LSI, and an integrated circuit for the functional blockmay be realized with a dedicated circuit or a general-purpose processor.Furthermore, if with advances in a semiconductor technology, atechnology of an integrated circuit that substitutes for the LSIappears, it is also possible to use an integrated circuit to which thetechnology applies.

Moreover, each functional block or various features of the base stationdevice and the terminal device used in each of the aforementionedembodiments may be implemented or executed by a circuitry, which istypically an integrated circuit or a plurality of integrated circuits.The circuitry designed to execute the functions described in the presentspecification may include a general-purpose processor, a digital signalprocessor (DSP), an application specific or general applicationintegrated circuit (ASIC), a field programmable gate array (FPGA), orother programmable logic devices, discrete gates or transistor logic, ora discrete hardware component, or a combination thereof. Thegeneral-purpose processor may be a microprocessor, or alternatively, theprocessor may be a conventional processor, a controller, amicrocontroller, or a state machine. The general-purpose processor oreach circuit described herein may be configured by a digital circuit ormay be configured by an analogue circuit. Further, when a technology ofmaking into an integrated circuit superseding integrated circuits at thepresent time appears due to advancement of a semiconductor technology,the integrated circuit by this technology is also able to be used.

As used herein, the term “and/or” should be interpreted to mean one ormore items. For example, the phrase “A, B and/or C” should beinterpreted to mean any of: only A, only B, only C, A and B (but not C),B and C (but not A), A and C (but not B), or all of A, B, and C. As usedherein, the phrase “at least one of” should be interpreted to mean oneor more items. For example, the phrase “at least one of A, B and C” orthe phrase “at least one of A, B or C” should be interpreted to mean anyof: only A, only B, only C, A and B (but not C), B and C (but not A), Aand C (but not B), or all of A, B, and C. As used herein, the phrase“one or more of” should be interpreted to mean one or more items. Forexample, the phrase “one or more of A, B and C” or the phrase “one ormore of A, B or C” should be interpreted to mean any of: only A, only B,only C, A and B (but not C), B and C (but not A), A and C (but not B),or all of A, B, and C.

<Sammary>

In one example, a user equipment (UE) comprising: receiving circuitryconfigured to receive a common configuration comprising parametersshared by multiple configured grants; and transmitting circuitryconfigured to perform, based on the parameters shared by the multipleconfigured grants of the common configuration, transmissions on aphysical uplink shared channel (PUSCH).

In one example, the UE wherein parameters in a specific configured grantoverwrite the parameters of the common configuration.

In one example, the UE wherein the parameters of the commonconfiguration overwrite parameters in a specific configured grant.

In one example, the UE wherein the shared parameters are included in aconfiguration for a primary configured grant.

In one example, the UE wherein a secondary configured grant follows theshared parameters included in the configuration for the primaryconfigured grant.

In one example, a base station apparatus comprising: transmittingcircuitry configured to transmit a common configuration comprisingparameters shared by multiple configured grants; and receiving circuitryconfigured to receive, based on the parameters shared by the multipleconfigured grants of the common configuration, transmissions on aphysical uplink shared channel (PUSCH).

In one example, the base station apparatus wherein parameters in aspecific configured grant overwrite the parameters of the commonconfiguration.

In one example, the base station apparatus wherein the parameters of thecommon configuration overwrite parameters in a specific configuredgrant.

In one example, the base station apparatus wherein the shared parametersare included in a configuration for a primary configured grant.

In one example, the base station apparatus wherein a secondaryconfigured grant follows the shared parameters included in theconfiguration for the primary configured grant.

In one example, a communication method of a user equipment (UE)comprising:

receiving a common configuration comprising parameters shared bymultiple configured grants; and performing, based on the parametersshared by the multiple configured grants of the common configuration,transmissions on a physical uplink shared channel (PUSCH).

In one example, the method wherein parameters in a specific configuredgrant overwrite the parameters of the common configuration.

In one example, the method wherein the parameters of the commonconfiguration overwrite parameters in a specific configured grant.

In one example, the method wherein the shared parameters are included ina configuration for a primary configured grant.

In one example, the method wherein a secondary configured grant followsthe shared parameters included in the configuration for the primaryconfigured grant.

In one example, a communication method of a base station apparatuscomprising:

transmitting a common configuration comprising parameters shared bymultiple configured grants; and receiving, based on the parametersshared by the multiple configured grants of the common configuration,transmissions on a physical uplink shared channel (PUSCH).

In one example, the method wherein parameters in a specific configuredgrant overwrite the parameters of the common configuration.

In one example, the method wherein the parameters of the commonconfiguration overwrite parameters in a specific configured grant.

In one example, the method wherein the shared parameters are included ina configuration for a primary configured grant.

In one example, the method wherein a secondary configured grant followsthe shared parameters included in the configuration for the primaryconfigured grant.

In one example, a user equipment (UE) that communicates with a basestation comprising: receiving circuitry configured to: receive a RadioResource Control (RRC) message including first information indicating arepetition type for a first configured grant (CG) Physical Uplink SharedChannel (PUSCH) transmission, receive a RRC message including secondinformation indicating a repetition type for a second CG PUSCHtransmission, receive a RRC message including third informationindicating whether codebook based transmission or non-codebook basedtransmission is used for the first CG PUSCH transmission and the secondCG PUSCH transmission, transmitting circuitry configured to: perform thefirst CG PUSCH transmission based on the first information and the thirdinformation, perform the second CG PUSCH transmission based on thesecond information and the third information.

In one example, a base station apparatus that communicates with a userequipment (UE) comprising: transmitting circuitry configured to:transmit a Radio Resource Control (RRC) message including firstinformation indicating a repetition type for a first configured grant(CG) Physical Uplink Shared Channel (PUSCH) transmission, transmit a RRCmessage including second information indicating a repetition type for asecond CG PUSCH transmission, transmit a RRC message including thirdinformation indicating whether codebook based transmission ornon-codebook based transmission is used for the first CG PUSCHtransmission and the second CG PUSCH transmission, receiving circuitryconfigured to: receive the first CG PUSCH transmission based on thefirst information and the third information, receive the second CG PUSCHtransmission based on the second information and the third information.

In one example, a communication method of a user equipment comprising:receiving a Radio Resource Control (RRC) message including firstinformation indicating a repetition type for a first configured grant(CG) Physical Uplink Shared Channel (PUSCH) transmission, receiving aRRC message including second information indicating a repetition typefor a second CG PUSCH transmission, receiving a RRC message includingthird information indicating whether codebook based transmission ornon-codebook based transmission is used for the first CG PUSCHtransmission and the second CG PUSCH transmission, performing the firstCG PUSCH transmission based on the first information and the thirdinformation, performing the second CG PUSCH transmission based on thesecond information and the third information.

In one example, a communication method of a base station apparatuscomprising: transmitting a Radio Resource Control (RRC) messageincluding first information indicating a repetition type for a firstconfigured grant (CG) Physical Uplink Shared Channel (PUSCH)transmission, transmitting a RRC message including second informationindicating a repetition type for a second CG PUSCH transmission,transmitting a RRC message including third information indicatingwhether codebook based transmission or non-codebook based transmissionis used for the first CG PUSCH transmission and the second CG PUSCHtransmission, receiving the first CG PUSCH transmission based on thefirst information and the third information, receiving the second CGPUSCH transmission based on the second information and the thirdinformation.

1. A user equipment (UE) that communicates with a base station comprising: receiving circuitry configured to: receive a Radio Resource Control (RRC) message including first information indicating that more than one configured grant (CG) Physical Uplink Shared Channel (PUSCH) transmission configuration is configured for the UE, receive a RRC message including second information indicating a repetition type for a first CG PUSCH transmission, receive a RRC message including third information indicating a repetition type for a second CG PUSCH transmission, and receive a RRC message including a parameter PUSCH-Config, and transmitting circuitry configured to: perform the first CG PUSCH transmission based on the second information and the parameter PUSCH-Config, and perform the second CG PUSCH transmission based on the third information and the parameter PUSCH-Config.
 2. A base station apparatus that communicates with a user equipment (UE) comprising: transmitting circuitry configured to: transmit a Radio Resource Control (RRC) message including first information indicating that more than one configured grant (CG) Physical Uplink Shared Channel (PUSCH) transmission configuration is configured for the UE, transmit a RRC message including second information indicating a repetition type for a first CG PUSCH transmission, transmit a RRC message including third information indicating a repetition type for a second CG PUSCH transmission, and transmit a RRC message including a parameter PUSCH-Config, and receiving circuitry configured to: receive the first CG PUSCH transmission based on the second information and the parameter PUSCH-Config, and receive the second CG PUSCH transmission based on the third information and the parameter PUSCH-Config.
 3. A communication method of a user equipment (UE) comprising: receiving a Radio Resource Control (RRC) message including first information indicating that more than one configured grant (CG) Physical Uplink Shared Channel (PUSCH) transmission configuration is configured for the UE, receiving a RRC message including second information indicating a repetition type for a first CG PUSCH transmission, receiving a RRC message including third information indicating a repetition type for a second CG PUSCH transmission, receiving a RRC message including a parameter PUSCH-Config, performing the first CG PUSCH transmission based on the second information and the parameter PUSCH-Config, and performing the second CG PUSCH transmission based on the third information and the parameter PUSCH-Config.
 4. (canceled) 